Re: pgsql: Non text modes for pg_dumpall, correspondingly change pg_restore
От | Andrew Dunstan |
---|---|
Тема | Re: pgsql: Non text modes for pg_dumpall, correspondingly change pg_restore |
Дата | |
Msg-id | 6e0e57e5-ace5-4d18-b1c1-7a3b3da36316@dunslane.net обсуждение исходный текст |
Ответ на | Re: pgsql: Non text modes for pg_dumpall, correspondingly change pg_restore (Álvaro Herrera <alvherre@kurilemu.de>) |
Ответы |
Re: pgsql: Non text modes for pg_dumpall, correspondingly change pg_restore
|
Список | pgsql-hackers |
On 2025-04-14 Mo 8:20 AM, Álvaro Herrera wrote: > On 2025-Apr-04, Andrew Dunstan wrote: > >> Non text modes for pg_dumpall, correspondingly change pg_restore > I think the new oid_string_list stuff in this commit is unnecessary, and > we can remove a bunch of lines by simplifying that to using > SimplePtrList, as the attached illustrates. (Perhaps the names of > members of the proposed struct can be improved.) Sure, we can do it that way. > > I also propose to remove the open-coded implementation of pg_get_line. > > WDYT? seems reasonable > > I'm also not sure about the double sscanf() business there ... There > must be a better way to do this. Yes, probably. I'll look into that if you like. cheers andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: