From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | PostgreSQL Development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] pg_pwd trigger to be removed |
Date: | 2000-03-07 23:39:24 |
Message-ID: | 200003072339.SAA00290@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
[Charset ISO-8859-1 unsupported, filtering to ASCII...]
> 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.
I think we liked the trigger, but wanted it to activate only on
transaction commit. I think Tom Lane had some ideas on this.
--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-03-07 23:40:23 | Re: [HACKERS] DROP TABLE inside a transaction block |
Previous Message | Bruce Momjian | 2000-03-07 23:35:35 | Re: [HACKERS] DROP TABLE inside a transaction block |