Re: [HACKERS] update_pg_pwd trigger does not work very well

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] update_pg_pwd trigger does not work very well
Date: 2000-02-27 05:35:42
Message-ID: 200002270535.AAA14214@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> I am not quite certain that this is completely bulletproof when there
> are multiple backends concurrently updating pg_shadow, but I have not
> been able to think of a case where it'd fail. The worst possibility
> is that a committed update in pg_shadow might not get propagated to
> pg_pwd for a while because some other transaction is holding a lock on
> pg_shadow. (But pg_pwd updates can be delayed for that reason now,
> so it's certainly no worse than before.)
>
> Comments?

I see your point. Guess we have to do it inside xact.

--
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

In response to

Responses

  • at 2000-02-27 05:52:14 from Ray Messier

Browse pgsql-hackers by date

  From Date Subject
Next Message Ray Messier 2000-02-27 05:52:14
Previous Message Tom Lane 2000-02-27 04:48:49 update_pg_pwd trigger does not work very well