| From: | Alexander Kukushkin <cyberdemn(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | David Fetter <david(at)fetter(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Statement timeout in pg_rewind |
| Date: | 2019-08-27 08:45:27 |
| Message-ID: | CAFh8B=no1sWzKs8sLSjFe7AGcdR2=w7XSSZdgdhYNWdvQKVocw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 27 Aug 2019 at 08:36, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> I'd rather be on the safe side and as we are looking at this at this
> area.. Who knows if this logic is going to change in the future and
> how it will change.
Agree.
> Oops, I misread this part. What about a simple wrapper
> run_simple_command which checks after PGRES_COMMAND_OK, and frees the
> result then? This could be used for the temporary table creation and
> when setting synchronous_commit.
Done, please see the next version attached.
Regards,
--
Alexander Kukushkin
| Attachment | Content-Type | Size |
|---|---|---|
| pg_rewind-statement_timeout-v2.patch | text/x-patch | 2.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ROS Didier | 2019-08-27 10:47:24 | PostgreSQL and Real Application Testing (RAT) |
| Previous Message | Rafia Sabih | 2019-08-27 08:36:06 | Re: Creating partitions automatically at least on HASH? |