Re: Re: COPY error: pqReadData() -- backend closed the channel unexpectedly

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tod McQuillin <devin(at)spamcop(dot)net>
Cc: Lee Joramo <lee(dot)list(at)joramo(dot)com>, rob <rob(at)cabrion(dot)com>, postgre general list <pgsql-general(at)postgresql(dot)org>
Subject: Re: Re: COPY error: pqReadData() -- backend closed the channel unexpectedly
Date: 2001-01-10 04:36:20
Message-ID: 8614.979101380@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tod McQuillin <devin(at)spamcop(dot)net> writes:
> I was not aware the binary would behave differently depending on the name
> it was invoked as.

Right. We used to have two separate binaries, and the postmaster would
actually exec() the backend (postgres) binary for every session launch.
About two years ago, Bruce made them into a single executable so that
session launch only needs fork() and not exec(). But he kept the old
switch-parsing mechanisms for backwards compatibiliy with existing
startup scripts. So our current switch syntax is a dreadfully ugly
legacy thingy :-(

Peter E. has done some good work towards providing a less ugly switch
notation for 7.1.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2001-01-10 04:43:57 Re: trouble with db-restore
Previous Message Martijn van Oosterhout 2001-01-10 04:20:24 Re: Re: Loading optimization