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

pg_pwd trigger to be removed

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: pg_pwd trigger to be removed
Date: 2000-03-05 13:29:50
Message-ID: Pine.LNX.4.21.0003051422190.347-100000@localhost.localdomain (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Because of the problems that were pointed out, I'm inclined to remove the
pg_pwd updating trigger again. I can offer you the non-initdb requiring
variant (just remove the trigger definition in initdb) or the
clean-sweeping one (remove the trigger function from the backend). Okay,
the first one will require some sort of intervention as well, eventually,
but you see the difference.

My new take on the situation is actually that there shouldn't be a reason
to tinker with the systems catalogs period. In the case of pg_shadow
that's not entirely possible (catupd and trace can't be adjusted
otherwise), but that can be fixed (not now). After all they're called
*system* catalogs. If someone thinks they can rename a table by updating
pg_class.relname -- good night!

Peter Eisentraut                  Sernanders väg 10:115
peter_e(at)gmx(dot)net                   75262 Uppsala            Sweden


pgsql-hackers by date

Next:From: Peter EisentrautDate: 2000-03-05 13:36:22
Subject: Re: [HACKERS] DROP TABLE inside a transaction block
Previous:From: Brian HirtDate: 2000-03-05 09:26:55
Subject: Optimizer badness in 7.0 beta

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