Re: [COMMITTERS] pgsql: Fix procedure for updating nextval() defaults

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Fix procedure for updating nextval() defaults
Date: 2005-10-04 01:24:56
Message-ID: 4341D9E8.5070505@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Didn't Alvaro write some script that we were going to use to help people
apply SQL changes against their databases?

Chris

Tom Lane wrote:
> Log Message:
> -----------
> Fix procedure for updating nextval() defaults so that it actually works.
> Update release dates for pending back-branch releases.
>
> Modified Files:
> --------------
> pgsql/doc/src/sgml:
> release.sgml (r1.386 -> r1.387)
> (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/release.sgml.diff?r1=1.386&r2=1.387)
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2005-10-04 01:38:06 Re: [COMMITTERS] pgsql: Fix procedure for updating nextval()
Previous Message Tom Lane 2005-10-03 23:43:46 pgsql: COPY's test for read-only transaction was backward; it prohibited

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Sabino Mullane 2005-10-04 01:28:41 Re: Last call for back-branch fixes
Previous Message Philip Yarra 2005-10-04 01:01:08 Re: RPMs for RedHat ES3.0