Re: Patch to implement pg_current_logfile() function

From: "Karl O(dot) Pinc" <kop(at)meme(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Gilles Darold <gilles(dot)darold(at)dalibo(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Patch to implement pg_current_logfile() function
Date: 2017-01-18 16:26:43
Views: Raw Message | Whole Thread | Download mbox
Lists: pgsql-hackers

On Wed, 18 Jan 2017 10:11:20 -0600
"Karl O. Pinc" <kop(at)meme(dot)com> wrote:

> You must write
> instead of just
> If you don't you get back 01000 for the error code.

> v26 patch attached which fixes this.

Attached are revised versions of the 2 (optional) patches which
make hardcoded constants into symbols to apply on
top of the v26 patch.

Karl <kop(at)meme(dot)com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein

Attachment Content-Type Size
patch_pg_current_logfile-v26.diff.abstract_guc_part1 application/octet-stream 2.6 KB
patch_pg_current_logfile-v26.diff.abstract_guc_part2 application/octet-stream 2.0 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Erik Rijkers 2017-01-18 16:35:30 Re: Logical replication existing data copy
Previous Message Corey Huinker 2017-01-18 16:24:10 Re: PSQL commands: \quit_if, \quit_unless