pg_pwd trigger to be removed - Mailing list pgsql-hackers

From Peter Eisentraut
Subject pg_pwd trigger to be removed
Date
Msg-id Pine.LNX.4.21.0003051422190.347-100000@localhost.localdomain
Whole thread Raw
Responses Re: [HACKERS] pg_pwd trigger to be removed  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: [HACKERS] pg_pwd trigger to be removed  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden



pgsql-hackers by date:

Previous
From: Brian Hirt
Date:
Subject: Optimizer badness in 7.0 beta
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] DROP TABLE inside a transaction block