Re: bytea vs. pg_dump
От | Magnus Hagander |
---|---|
Тема | Re: bytea vs. pg_dump |
Дата | |
Msg-id | 9837222c0908040732q764e0de3xe28ff9fa5011c855@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: bytea vs. pg_dump (Robert Haas <robertmhaas@gmail.com>) |
Список | pgsql-hackers |
On Tue, Aug 4, 2009 at 16:31, Robert Haas<robertmhaas@gmail.com> wrote: > On Tue, Aug 4, 2009 at 10:28 AM, Tom Lane<tgl@sss.pgh.pa.us> wrote: >> Peter Eisentraut <peter_e@gmx.net> writes: >>> On Monday 03 August 2009 22:11:08 Tom Lane wrote: >>>> I'm starting to look at this patch. I observe that it's setting the >>>> default output format to HEX. If changing the default behavior was >>>> agreed to, or even discussed, I do not remember where. Shouldn't the >>>> default stay the same? >> >>> I did pose that question in my patch submission email. >> >>> Unless there is overwhelming support in favor of changing, we probably >>> shouldn't change it, at least not yet. >> >> While I've been poking at the pg_dump issues, it's occurred to me that >> changing the default would be a great forcing function for finding out >> any lurking problems. What I'm inclined to do now is to commit it >> *with* the change of default, and let it be that way at least for a >> few alpha-test releases. We can vote on whether to switch the default >> back before 8.5 final. >> >> If this seems reasonable, I can make a note of the point in the commit >> message, so that we won't forget when the time comes. > > Or, what we could do is start an open items for 8.5 list similar to > the one we made for 8.4. That worked pretty well, I think. +1 for that solution, it seems much better than having to go back through commit messages. We might as well start it early! -- Magnus HaganderSelf: http://www.hagander.net/Work: http://www.redpill-linpro.com/
В списке pgsql-hackers по дате отправления: