Re: Re: COPY error: pqReadData() -- backend closed the channel unexpectedly
От | Bruce Momjian |
---|---|
Тема | Re: Re: COPY error: pqReadData() -- backend closed the channel unexpectedly |
Дата | |
Msg-id | 200101112125.QAA07430@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: Re: COPY error: pqReadData() -- backend closed the channel unexpectedly (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Re: COPY error: pqReadData() -- backend closed the channel unexpectedly
|
Список | 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 по дате отправления: