Re: postgres hot-standby questions. - Mailing list pgsql-admin

From Graeme B. Bell
Subject Re: postgres hot-standby questions.
Date
Msg-id 8A0640B6-CE88-4E03-B145-0B6149DE7173@skogoglandskap.no
Whole thread Raw
In response to Re: postgres hot-standby questions.  ("Graeme B. Bell" <grb@skogoglandskap.no>)
Responses Re: postgres hot-standby questions.
List pgsql-admin
> With fully synchronous replication the performance issue is a real killer for us.
> I suppose what I'm wondering is about async normal operation, but sync operation during shutdown.


Replying to myself - but a further thought -

Assuming that you have your server configured with 1 or more hot standbys.
Are there situations where it is smart & sane to allow a controlled (slow, not emergency) shutdown to complete
asynchronouslywithout knowing if any standby got the last bits of wal? 

Should a fully async shutdown with a connected standby ever happen?

You've no guarantee the standbys are up to date. Since the server is shutdown, you've no way to ask it and check
withoutlooking at the filesystem directly.  
I guess the problem with "eventually consistent" is that during shutdown you know for sure that 'eventually' isn't ever
goingto happen unless you make it happen.  

Graeme.



pgsql-admin by date:

Previous
From: Scott Ribe
Date:
Subject: Re: postgres hot-standby questions.
Next
From: Scott Ribe
Date:
Subject: Re: postgres hot-standby questions.