Re: Statistics Import and Export
| От | Corey Huinker |
|---|---|
| Тема | Re: Statistics Import and Export |
| Дата | |
| Msg-id | CADkLM=fF2ak7Dh90XFhm-wDv6ELaJstOdZwGZCx400Yn4LJUqA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Statistics Import and Export (Andres Freund <andres@anarazel.de>) |
| Ответы |
Re: Statistics Import and Export
|
| Список | pgsql-hackers |
I don't follow. We already have the tablenames, schemanames and oids of the
to-be-dumped tables/indexes collected in pg_dump, all that's needed is to send
a list of those to the server to filter there?
Do we have something that currently does that? All of the collect functions (collectComments, etc) take an unfiltered approach. Seems like we'd have to collect the stats sometime after ProcessArchiveRestoreOptions, which is significantly after the rest of them.
My concern is that it might prevent some upgrades from *ever* completing,
because of pg_dump running out of memory.
Obviously a valid concern.
В списке pgsql-hackers по дате отправления: