The following bug has been logged on the website:
Bug reference: 13287
Logged by: Hillel Eilat
Email address: Hillel.Eilat@attunity.com
PostgreSQL version: 9.4.1
Operating system: Windows 7
Description:
Hello
I am in a process of developing an REPLICATION application using PostgreSQL
9.4.1 on a "Windows 7" platform.
"Logical Decoding" feature is used for extracting database changes in
real-time.
A dedicated replication slot - say [Replication Slot Name] - is used for
controlling this flow.
Everything works fine until PostgreSQL service is stopped.
While an active replication slot exists and PostgreSQL service is neatly
stopped, further attempt to restart it is responded by:
PostgreSQL - PANIC: could not fsync file "pg_replslot/[Replication Slot
Name]/state": Bad file descriptor
Actually - the database in question is now corrupted / not operational
anymore.
Tonight this occurred also after a spontaneous machine shutdown.
This misbehavior now occurs very systematically upon stopping PostgreSQL
service while active replication slots are defined there.
Your help will be appreciated.
Hillel.