jkilborn <jim.kilborn@swri.org> writes:
> Thanks for the reply.
>
> I think the problem is permissions. The fact that the pgpool runs as root
> user, its likely that postgres canât remove the created trigger file.
Right /tmp usually has sticky bit set and thus though the directory is
world writeable, one user can't remove a file owned by another as is
the case here.
And IMO having trigger file be in tmp isn't a great idea since anyone on
the box could create the file and have your standby server come out of recovery.
> I ended up doing two things in my pgp failover_stream.sh script, which
> creates the file:
> /bin/ssh -T $new_master /bin/touch $trigger_file
> /bin/ssh -T $new_master chown postgres $trigger_file
>
> Seems with changing the ownership of the trigger file, postgres can now
> delete the file. Not sure why Iâm having to do this, as I havenât seen
> anyone else encounter this issue.
>
> Anyway, with these changes, it appears to be working correctly.
>
> Thanks for the response.
>
> -Jim
>
>
>
>
> --
> View this message in context: http://postgresql.nabble.com/postgres-not-deleting-trigger-file-tp5860795p5860802.html
> Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres.consulting@comcast.net
p: 312.241.7800