Thread

  1. Hot Standby status

    Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> — 2009-11-10T18:36:56Z

    Attached is the latest and greatest patch against CVS head, taken from
    the hs-riggs branch in my git repository.
    
    These two TODO items I listed earlier have now been fixed:
    
    > <done> allow connections after a shutdown checkpoint
    >
    > <done> don't clear locks belonging to prepared transactions at startup
    
    And these still remain:
    
    > - clarify default_transaction_read_only and transaction_read_only
    >
    http://archives.postgresql.org/message-id/4AB75A61.6040505@enterprisedb.com
    >
    > - 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.8050305@enterprisedb.com)
    >
    > - connection goes out of sync when an idle-in-transaction transaction is
    > killed
    >
    (http://archives.postgresql.org/message-id/4ACF77A5.1070706@enterprisedb.com)
    
    Those are pretty small things, shouldn't take long to fix. After all of
    those TODO items have been addressed, the patch needs a round or two of
    cleanup. Things have been moved around and changed so much that many of
    the functions are probably not in a good place in code anymore.
    
    As I said before:
    
    > 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.
    
    -- 
      Heikki Linnakangas
      EnterpriseDB   http://www.enterprisedb.com
    
  2. Re: Hot Standby status

    Devrim GÜNDÜZ <devrim@gunduz.org> — 2009-11-10T20:00:30Z

    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
    
  3. Re: Hot Standby status

    Michael Glaesemann <grzm@seespotcode.net> — 2009-11-10T20:11:07Z

    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
    
    
    
    
    
  4. Re: Hot Standby status

    Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> — 2009-11-11T07:54:27Z

    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
    
    
  5. Re: Hot Standby status

    Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> — 2009-11-11T08:03:33Z

    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
    
    
  6. Re: Hot Standby status

    Simon Riggs <simon@2ndquadrant.com> — 2009-11-11T13:21:35Z

    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
    
    
    
  7. Re: Hot Standby status

    Simon Riggs <simon@2ndquadrant.com> — 2009-11-11T13:23:13Z

    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