Re: [HACKERS] Hot Standby status
Devrim GÜNDÜZ wrote: Is there a reason why recovery.conf.sample does not include (sample) entries for recovery_connections and max_standby_delay? No, they probably should be included. I'll add them, thanks. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Hot Standby status
On Tue, 2009-11-10 at 22:00 +0200, Devrim GÜNDÜZ wrote: On Tue, 2009-11-10 at 20:36 +0200, Heikki Linnakangas wrote: Attached is the latest and greatest patch against CVS head, taken from the hs-riggs branch in my git repository. Is there a reason why recovery.conf.sample does not include (sample) entries for recovery_connections and max_standby_delay? No reason. I'll add entries for those. -- Simon Riggs www.2ndQuadrant.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Hot Standby status
On Tue, 2009-11-10 at 15:11 -0500, Michael Glaesemann wrote: I skimmed through the documentation to get a better handle on what this will mean. Thanks for this and any further corrections/additions. -- Simon Riggs www.2ndQuadrant.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Hot Standby status
On Tue, 2009-11-10 at 20:36 +0200, Heikki Linnakangas wrote: Attached is the latest and greatest patch against CVS head, taken from the hs-riggs branch in my git repository. Is there a reason why recovery.conf.sample does not include (sample) entries for recovery_connections and max_standby_delay? Regards, -- Devrim GÜNDÜZ, RHCE Command Prompt - http://www.CommandPrompt.com devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr http://www.gunduz.org Twitter: http://twitter.com/devrimgunduz signature.asc Description: This is a digitally signed message part
Re: [HACKERS] Hot Standby status
On Nov 10, 2009, at 13:36 , Heikki Linnakangas wrote: Attached is the latest and greatest patch against CVS head, taken from the hs-riggs branch in my git repository. Awesome. Thank you, Simon and Heikki! I skimmed through the documentation to get a better handle on what this will mean. + para + These actions produce error messages + + itemizedlist +listitem + para + DML - Insert, Update, Delete, COPY FROM, Truncate. + Note that there are no actions that result in a trigger + being executed during recovery. + /para + /listitem +listitem + para + DDL - Create, Drop, Alter, Comment (even for temporary tables because + currently these cause writes to catalog tables) + /para + /listitem Other commands are in all-caps. Any reason INSERT, UPDATE, DELETE, TRUNCATE, CREATE, DROP, ALTER, and COMMENT are not? Cheers, Michael Glaesemann grzm seespotcode net -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Hot Standby status
Michael Glaesemann wrote: Other commands are in all-caps. Any reason INSERT, UPDATE, DELETE, TRUNCATE, CREATE, DROP, ALTER, and COMMENT are not? No. Thanks, I'll fix that. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Hot standby status
On Thu, 2009-10-15 at 10:33 +0300, Heikki Linnakangas wrote: There's been a lot of churn in hot standby since the beginning of the commitfest, so I thought it would be good to summarize where we are. Attached is the latest and greatest patch against CVS head, taken from the hs-riggs branch in my git repository where I've been working on this. Here's a list of TODOs/issues that've already been mentioned. - clarify default_transaction_read_only and transaction_read_only http://archives.postgresql.org/message-id/4ab75a61.6040...@enterprisedb.com Yes, still outstanding. This is the only unfixed issue I am aware of. It's not that big a deal, hence why its bottom of the pile. Anyway, will fix. The other issues are fixed in one or other of the current dev trees. - allow connections after a shutdown checkpoint - don't clear locks belonging to prepared transactions at startup - rename references to loggable locks to AccessExclusiveLocks in master or similar - race condition in xact_redo_commit/abort (http://archives.postgresql.org/message-id/4abf539f.8050...@enterprisedb.com) Not sure about those ones, as yet, but I do have 9 unapplied patches to move from my tree to the shared one. - connection goes out of sync when an idle-in-transaction transaction is killed (http://archives.postgresql.org/message-id/4acf77a5.1070...@enterprisedb.com) I reported that myself in September and fixed it before your report. So I guess there is some more code to move across as well. Before this is committed, there's some debug code that ought to be removed: - PostAuthDelay in startup process. Or maybe that should be left in, but some doc changes would then be in order. I'm inclined to remove it though. Happy if you'd like to remove it. - the CleanupWaitStats stuff. If we want something like this, I'd like to see it integrated into existing pg_stat views. Would like to leave it in, but only for now. We can always remove it before production. So far I've never seen it block there, so I'm interested in whether its worth the effort to track it more formally through stats. I regard this as in the same area as trace_sort, i.e. developer info. Let me know if I'm missing something. And please feel free to help, by testing, by reviewing and commenting on the patch, or by addressing any of the above issues. I will continue working on this, but this is a big patch so any help is much appreciated. Hopefully this comment isn't at me! I've been down for a few days with laptop problems, slowly re-installing everything (for those laughing, yes, I had a backup). -- Simon Riggs www.2ndQuadrant.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Hot standby status
Simon Riggs wrote: On Thu, 2009-10-15 at 10:33 +0300, Heikki Linnakangas wrote: Let me know if I'm missing something. And please feel free to help, by testing, by reviewing and commenting on the patch, or by addressing any of the above issues. I will continue working on this, but this is a big patch so any help is much appreciated. Hopefully this comment isn't at me! Heh, no, I know you're working on it. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
