Thread: BUG #15278: When initialising Streaming Slave if some folders andfiles are symlinks they are not copied over

The following bug has been logged on the website:

Bug reference:      15278
Logged by:          Areg Vrtanesyan
Email address:      vrtareg@yahoo.com
PostgreSQL version: 9.6.9
Operating system:   Linux RHE7.4
Description:

Hi

I was creating streaming slave using
https://wiki.postgresql.org/wiki/Streaming_Replication WiKi

Now when I have moved some of my config files to another place to keep them
in SVN and also log folders to another partition streaming initialisation
produces warnings.

Not sure if they are safe as pg_clog will be empty ...



WARNING:  skipping special file "./pg_hba.conf"
WARNING:  skipping special file "./pg_ident.conf"
WARNING:  skipping special file "./postgresql.auto.conf"
WARNING:  skipping special file "./postgresql.conf"
WARNING:  skipping special file "./pg_clog"
WARNING:  skipping special file "./pg_log"
WARNING:  skipping special file "./pg_hba.conf"
WARNING:  skipping special file "./pg_ident.conf"
WARNING:  skipping special file "./postgresql.auto.conf"
WARNING:  skipping special file "./postgresql.conf"
WARNING:  skipping special file "./pg_clog"
WARNING:  skipping special file "./pg_log"

Regards,
Areg


On Mon, Jul 16, 2018 at 08:34:35AM +0000, PG Bug reporting form wrote:
> I was creating streaming slave using
> https://wiki.postgresql.org/wiki/Streaming_Replication WiKi
>
> Now when I have moved some of my config files to another place to keep them
> in SVN and also log folders to another partition streaming initialisation
> produces warnings.
>
> Not sure if they are safe as pg_clog will be empty ...

That's unsafe for pg_clog as this tracks the transaction commit status
based on the transaction ID.  Note that this is not a bug, a base backup
using the replication protocol allows only symlinks to be in pg_tblspc,
and pg_wal (pg_xlog for <= 9.6) is handled as a special case.
--
Michael

Attachment
Hi Michael 

I was assuming that too.

I will consider to move pg_clog back.


Regards,
Areg

On Mon, 16 Jul 2018 at 13:49, Michael Paquier
<michael@paquier.xyz> wrote:
On Mon, Jul 16, 2018 at 08:34:35AM +0000, PG Bug reporting form wrote:
> I was creating streaming slave using
> https://wiki.postgresql.org/wiki/Streaming_Replication WiKi
>
> Now when I have moved some of my config files to another place to keep them
> in SVN and also log folders to another partition streaming initialisation
> produces warnings.
>
> Not sure if they are safe as pg_clog will be empty ...

That's unsafe for pg_clog as this tracks the transaction commit status
based on the transaction ID.  Note that this is not a bug, a base backup
using the replication protocol allows only symlinks to be in pg_tblspc,
and pg_wal (pg_xlog for <= 9.6) is handled as a special case.
--
Michael
Attachment