Re: postgres not deleting trigger file

Are either the pgpool or postgresql logs telling you anything about this?
Usually, at least I think so, PostgreSQL is responsible for removing the
trigger file. I'll tell you, though, I haven't tried this type of scenario
since PostgreSQL 9.3.6.
--
Jay

On Tue, Aug 4, 2015 at 7:46 AM, jkilborn <jim(dot)kilborn(at)swri(dot)org> wrote:

> Im using postgres 9.4 with pgpool-II-94 and have streaming resplication
> setup
> between two db servers. When I fail the primary db, pgpool creates the
> /tmp/trigger_file, and the secondary server becomes the primary and is put
> in read/write mode. However, the trigger file doesnt get deleted. I am not
> sure where to debug why the trigger file doesnt get removed.
>
> I have even tried using a recover_end_command to remove the trigger file,
> but that doesnt seem to happen.
>
> my failover script for pgpool creates the trigger file, then set it to
> chmod
> 777 so that postgres user can remove it. pgpool runs as root, while
> postgres
> runs as postgres user.
>
> Any ideas where to look on this issue of trigger file not being removed?
>
>
>
>
>
> --
> View this message in context:
> http://postgresql.nabble.com/postgres-not-deleting-trigger-file-tp5860795.html
> Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
>
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>