Skip site navigation (1) Skip section navigation (2)

Re: [COMMITTERS] pgsql: Fix two bugs in change_owner_recurse_to_sequences: it was

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Fuhr <mike(at)fuhr(dot)org>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>,PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Fix two bugs in change_owner_recurse_to_sequences: it was
Date: 2005-03-26 07:30:28
Message-ID: 11304.1111822228@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
Michael Fuhr <mike(at)fuhr(dot)org> writes:
> I brought this up a few months ago.  Tom, weren't your objections
> based more on implementation concerns than on whether the idea
> itself had merit?

No, my point was that making implicit sequences work transparently
requires more thought than this.  I'd like to see a fairly complete
plan put forward before we start installing random hacks on permissions.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Devrim GUNDUZDate: 2005-03-26 10:14:28
Subject: Re: pg_dump issue : Cannot drop a non-existent(?) trigger
Previous:From: chamil wijenayakeDate: 2005-03-26 07:11:19
Subject: i want to find

pgsql-committers by date

Next:From: seancDate: 2005-03-26 19:01:56
Subject: pgmemcache: pgmemcache Makefile.pmk pgmemcache.c
Previous:From: Michael FuhrDate: 2005-03-26 06:55:08
Subject: Re: [COMMITTERS] pgsql: Fix two bugs in change_owner_recurse_to_sequences: it was

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group