Re: Re: COPY error: pqReadData() -- backend closed the channel unexpectedly - Mailing list pgsql-general

From Bruce Momjian
Subject Re: Re: COPY error: pqReadData() -- backend closed the channel unexpectedly
Date
Msg-id 200101112125.QAA07430@candle.pha.pa.us
Whole thread Raw
In response to Re: Re: COPY error: pqReadData() -- backend closed the channel unexpectedly  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Re: COPY error: pqReadData() -- backend closed the channel unexpectedly  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
> Tod McQuillin <devin@spamcop.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.

Tom, can you be a little more specific on the changes?  I am unsure of
the details.

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

pgsql-general by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Re: Loading optimization
Next
From: "J.H.M. Dassen (Ray)"
Date:
Subject: Re: How to set "auto commit" off in postgresql db?