| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Florian Pflug <fgp(dot)phlo(dot)org(at)gmail(dot)com> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, Andrew Chernow <ac(at)esilo(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PATCHES] libpq type system 0.9a |
| Date: | 2008-04-09 19:57:06 |
| Message-ID: | 26617.1207771026@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Florian Pflug <fgp(dot)phlo(dot)org(at)gmail(dot)com> writes:
> But isn't that an argument *for* having support for the binary format in
> libpq in a form similar to what this patch offers? Then at least you'd
> be safe as long as your libpq-version is >= your server version.
> Currently, there seems to be no safe way to use the binary format,
That's right, there isn't, and it's folly to imagine that anything like
this will make it "safe".
What we really put in the binary I/O support for was for COPY BINARY,
with a rather limited use-case of fast dump and reload between similar
server versions (you'll notice pg_dump does NOT use it). Yeah, we
expose it for clients to use, but they had better understand that they
are increasing their risk of cross-version portability problems.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-04-09 20:25:29 | Re: [PATCHES] libpq type system 0.9a |
| Previous Message | Tom Lane | 2008-04-09 19:50:51 | Re: Segfault using heap_form_tuple |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-04-09 20:25:29 | Re: [PATCHES] libpq type system 0.9a |
| Previous Message | Magnus Hagander | 2008-04-09 19:54:39 | Re: Fix for win32 stat() problems |