Re: Inconsistent error handling in START_REPLICATION command

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Inconsistent error handling in START_REPLICATION command
Дата
Msg-id 29286.1457719903@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Inconsistent error handling in START_REPLICATION command  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: Inconsistent error handling in START_REPLICATION command  (David Steele <david@pgmasters.net>)
Список pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Fri, Mar 11, 2016 at 11:36 AM, David Steele <david@pgmasters.net> wrote:
>> It looks like a decision needs to be made here whether to apply this patch,
>> send it back to the author, or reject it so I'm marking it "Ready for
>> Committer".
>> 
>> Robert, since you were participating in this conversation can you have a
>> look?

> Who, me?  *looks around*
> 
> OK, I had a look.  I don't think this is a bug.

I agree, and Craig's complaint that this change reduces flexibility
for plugins seems to tilt the balance against it.  I see that Alex
himself accepted that argument in his last message in the thread
(<CACACo5Sm-tY-9YijuLbXmcLmSkYtcTaVQh_1j4tADfjC+1-bCw@mail.gmail.com>).
So let's mark it rejected and move on.

> unexpected PQresultStatus: 8

It is a bit annoying that psql doesn't print "COPY_BOTH" here.
But fixing that is not this patch, either.
        regards, tom lane



В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Joshua D. Drake"
Дата:
Сообщение: Re: Freeze avoidance of very large table.
Следующее
От: David Steele
Дата:
Сообщение: Re: eXtensible Transaction Manager API (v2)