On Wed, Feb 24, 2021 at 02:29:31PM +0900, Michael Paquier wrote:
> Yeah, let's fix that. Adding only PGDATABASE to the list of
> environment variables supported does not look enough to me, so I
> propose the simple patch attached to clarify what happens to dbname in
> more details.
Applied this o
On Wed, Feb 24, 2021 at 08:15:59PM +0900, Fujii Masao wrote:
> But I have one question; why do those commands use different
> archive directories? Isn't it better to use the same one?
storage.sgml uses /var/lib/pgsql/data for the location of the data,
and the archive path is a mix between /mnt/ser
On Wed, Feb 24, 2021 at 11:16:57PM +1000, Dmitriy Kuzmin wrote:
> Will this change be made in the documentation for all Postgresql versions?
This wording has been introduced back in 2011 as of b186523, and
nobody complained about that until now, so I did not see a strong need
to back-patch it. Wo
Thanks.
Will this change be made in the documentation for all Postgresql versions?
Best regards,
Dmitriy Kuzmin
ср, 24 февр. 2021 г. в 12:19, Michael Paquier :
> On Sun, Feb 21, 2021 at 09:21:41PM -0300, Euler Taveira wrote:
> > LGTM.
>
> Thanks, applied.
> --
> Michael
>
On 2021/02/24 16:52, Michael Paquier wrote:
On Wed, Feb 24, 2021 at 07:24:17AM +0100, Philipp Gramzow wrote:
I agree, using a proper extension would be more straightforward. I'm sure
that's the reason why someone changed our archive_command.
Okay, let's do so in the docs then. Others may h
