From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bernd Helmle <mailings(at)oopsware(dot)de> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Subject: | Re: bytea vs. pg_dump |
Date: | 2009-08-04 16:21:54 |
Message-ID: | 25745.1249402914@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bernd Helmle <mailings(at)oopsware(dot)de> writes:
> --On Samstag, Juli 11, 2009 13:40:44 +0300 Peter Eisentraut
> <peter_e(at)gmx(dot)net> wrote:
>> OK, here is an updated patch. It has the setting as enum, completed
>> documentation, and libpq support. I'll add it to the commit fest in the
>> hope that someone else can look it over in detail.
> I've attached a slightly edited patch which fixes a compiler warning in
> encode.c, too.
Committed with assorted corrections. I have not done anything about
the issues mentioned in
http://archives.postgresql.org/message-id/21837.1248215656@sss.pgh.pa.us
mainly that pg_dump's treatment of large-object contents is not safe
against changes of standard_conforming_strings. I think that ought to
get dealt with before moving on.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2009-08-04 16:24:40 | Re: Alpha Releases: Docs? |
Previous Message | Bernd Helmle | 2009-08-04 16:19:53 | Re: bytea vs. pg_dump |