Skip site navigation (1) Skip section navigation (2)

Re: Loading binary data into the database

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: a(dot)joubert(at)albourne(dot)com, Postgresql <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: Loading binary data into the database
Date: 2000-07-27 14:17:29
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
> Adriaan Joubert <a(dot)joubert(at)albourne(dot)com> writes:
> > since 7.0.2 binary copy has been disabled, making
> > quite a few libpq functions superfluous
> Such as?  IIRC, the reason we disabled it was precisely that there was
> no support on the client side.  (What's worse, there's no support in
> the FE/BE protocol either.  I don't see how you could have made this
> work...)
> Cross-machine binary copy is a dangerous thing anyway, since it opens
> you up to all sorts of compatibility problems.  If your app is running
> on the same machine as the server, you can write data to a file and
> then send a command to do a binary copy from that file.

We disabled binary copy?  Using \copy or COPY?

  Bruce Momjian                        |
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In response to


pgsql-hackers by date

Next:From: Zeugswetter Andreas SBDate: 2000-07-27 14:22:41
Subject: AW: AW: AW: AW: AW: Vacuum only with 20% old tuples
Previous:From: Tom LaneDate: 2000-07-27 14:03:42
Subject: Re: AW: AW: AW: AW: Vacuum only with 20% old tuples

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group