Re: pgsql: Add pg_postmaster_start_time() function. - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql: Add pg_postmaster_start_time() function.
Date
Msg-id 2514.1118844696@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: Add pg_postmaster_start_time() function.  (Neil Conway <neilc@samurai.com>)
List pgsql-committers
Neil Conway <neilc@samurai.com> writes:
> Bruce Momjian wrote:
>> Add pg_postmaster_start_time() function.

> You should have bumped the catversion, no?

Probably, but it's not essential since nothing depends on that pg_proc
entry being there.  If, for instance, he'd added a regression test
using it then a catversion bump would be required IMHO.

I had a similar situation a few days ago when I was taking out the unary
% and ^ operators: a catversion bump could have been called for, but I
felt it was OK to not do it.  Running with the old pg_operator contents
wouldn't have any ill effects.

Part of the reason for being lazy here is that I'm quite sure there will
be more catversion bumps before 8.1 goes final; so the only question is
whether anyone's development installation is likely to fail if they run
an updated postmaster without initdb'ing.  If I thought these might be
the last catalog changes before a release, I'd want a catversion bump
so we could be certain everyone running a release postmaster has release
catalogs.

            regards, tom lane

pgsql-committers by date:

Previous
From: momjian@svr1.postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Fix display of database name during autovacuum.
Next
From: Tom Lane
Date:
Subject: Re: pgsql: Add BETWEEN SYMMETRIC.