Re: CVS corruption/mistagging?

From: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Kris Jurka <books(at)ejurka(dot)com>, Michael Meskes <meskes(at)postgresql(dot)org>, Marc Fournier <scrappy(at)hub(dot)org>
Subject: Re: CVS corruption/mistagging?
Date: 2007-08-15 16:07:02
Message-ID: 46C324A6.4080603@kaltenbrunner.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut wrote:
> Am Mittwoch, 15. August 2007 04:20 schrieb Tom Lane:
>> we should at least log such commands, and maybe disallow to anyone
>> except Marc's "pgsql" account.
>
> I don't think we should disallow it. Or otherwise we might one day be stuck
> if we need to release while some specific person is on vacation.

Is this really a problem in practise ?
If such a need arises any commiter (or sysadmin) would probably be able
to remove that restriction in a few minutes.
I think the point here is to prevent such things done by accident(vs. on
purpose) which a script like that seems like a fairly simple yet
effective solution.

Stefan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2007-08-15 16:08:32 Re: [mmoncure@gmail.com: Re: [GENERAL] array_to_set functions]
Previous Message Bruce Momjian 2007-08-15 16:01:39 XID wraparound and busy databases