Re: pg_dump output portability
От
Peter Eisentraut
Тема
Re: pg_dump output portability
Дата
Msg-id
Pine.LNX.4.44.0208152126500.20055-100000@localhost.localdomain
Ответ на
Re: pg_dump output portability (Tom Lane)
Список
Дерево обсуждения
pg_dump output portability Peter Eisentraut <peter_e@gmx.net>
Re: pg_dump output portability Rod Taylor <rbt@zort.ca>
Re: pg_dump output portability Bruce Momjian <pgman@candle.pha.pa.us>
Re: pg_dump output portability Tom Lane <tgl@sss.pgh.pa.us>
Re: pg_dump output portability Peter Eisentraut <peter_e@gmx.net>
Re: pg_dump output portability Tom Lane <tgl@sss.pgh.pa.us>
Re: pg_dump output portability Peter Eisentraut <peter_e@gmx.net>
Re: pg_dump output portability Tom Lane <tgl@sss.pgh.pa.us>
Re: pg_dump output portability Bruce Momjian <pgman@candle.pha.pa.us>
Re: pg_dump output portability Rod Taylor <rbt@zort.ca>
Tom Lane writes: > Ah. But where exactly will you substitute true for 't'? I don't think > pg_dump necessarily knows enough to apply that transformation. Sure, it does it already for other types. Look for BITOID in pg_dump.c. > Switching the default is definitely fine with me, but I'd lean towards > ripping it out entirely, given that the backend-supplied chunks of stuff > are not going to have extra quotes. We always tell people "always quote > or never quote" a given identifier; pg_dump scripts ought to follow that > rule. It occurred to me that pg_dump would need to know which names are keywords. Ugh. -- Peter Eisentraut peter_e@gmx.net
В списке pgsql-hackers по дате отправления