Re: OOM in libpq and infinite loop with getCopyStart()
От | Robert Haas |
---|---|
Тема | Re: OOM in libpq and infinite loop with getCopyStart() |
Дата | |
Msg-id | CA+TgmoY50gsFnsODQe1AnTh7JZQ4LGonSrU6i-KEJE5Of7d+AA@mail.gmail.com обсуждение исходный текст |
Ответ на | OOM in libpq and infinite loop with getCopyStart() (Michael Paquier <michael.paquier@gmail.com>) |
Ответы |
Re: OOM in libpq and infinite loop with getCopyStart()
|
Список | pgsql-hackers |
On Tue, Mar 1, 2016 at 12:38 AM, Michael Paquier <michael.paquier@gmail.com> wrote: > Thoughts? I have registered that in the CF app, and a patch is attached. It is very difficult to believe that this is a good idea: --- a/src/backend/replication/libpqwalreceiver/libpqwalreceiver.c +++ b/src/backend/replication/libpqwalreceiver/libpqwalreceiver.c @@ -445,6 +445,7 @@ libpqrcv_PQexec(const char *query) if (PQresultStatus(lastResult) == PGRES_COPY_IN || PQresultStatus(lastResult) == PGRES_COPY_OUT || PQresultStatus(lastResult) == PGRES_COPY_BOTH || + PQresultStatus(lastResult) == PGRES_FATAL_ERROR || PQstatus(streamConn) == CONNECTION_BAD) break; } I mean, why would it be a good idea to blindly skip over fatal errors? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: