Re: bytea vs. pg_dump

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Bernd Helmle" <mailings(at)oopsware(dot)de>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: bytea vs. pg_dump
Date: 2009-05-05 20:32:35
Message-ID: 4A005C13.EE98.0025.0@wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Unless we can think of a more bulletproof format selection mechanism

Would it make any sense to have an option on the COPY command to tell
it to use base64 for bytea columns?

-Kevin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2009-05-05 20:57:50 Re: bytea vs. pg_dump
Previous Message Tom Lane 2009-05-05 20:14:54 Re: bytea vs. pg_dump