Re: [pgsql-patches] pg_dump pretty_print

Поиск
Список
Период
Сортировка
От Greg Sabino Mullane
Тема Re: [pgsql-patches] pg_dump pretty_print
Дата
Msg-id 57777b8d126d1f02471da7f0cdfa8a82@biglumber.com
обсуждение исходный текст
Ответы Re: [pgsql-patches] pg_dump pretty_print  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


Peter Eisentraut replied:

> The harm here is that under undefined circumstances a dump file
> will not be a proper and robust representation of the original
> database, which would add significant confusion and potential for error.

What "undefined circumstances" are we talking here? If there is a chance
that pg_get_viewdef and company do not output a version that can be
read again by the database because we simply changed the whitespace, that
sounds like a serious bug to be fixed, not a reason to reject this
optional flag.

- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200701251003
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iD8DBQFFuXd2vJuQZxSWSsgRA9VDAJ9S1b+4DJomO3Bmij4wvida9wtgfgCeID16
qeoNrrehtTGIeJeL8T+mx9M=
=VecV
-----END PGP SIGNATURE-----



В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Simon Riggs"
Дата:
Сообщение: HAVING push-down
Следующее
От: Hannu Krosing
Дата:
Сообщение: Re: Proposal: Snapshot cloning