pg.ddx.io pgsql-sql@postgresql.org mailing list archivehelp / color / mirror / Atom feed
Record Lock details 2+ messages / 2 participants [nested] [flat]
* Record Lock details @ 2004-04-23 08:43 Denis P Gohel <sqllist@coralindia.com> 2004-04-23 10:03 ` Re: Record Lock details Peter Eisentraut <peter_e@gmx.net> 0 siblings, 1 reply; 2+ messages in thread From: Denis P Gohel @ 2004-04-23 08:43 UTC (permalink / raw) To: pgsql-sql Hi all, I am using PostgreSQL 7.3.1. Is there a data dictionary in Postgres from where i can get the info about locked rows of any table ? If possible the value of those locked record ? My situation is like: I have an ODBC application working on Postgres. There are Master child tables. I want, if a user A is editing any document ( one master and set of child records) in front-end application, the same should not be available to other user for editing. I thought of using SELECT FOR UPDATE. But, in my case, i need to display the name of application user and other details about the locked row. ^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Record Lock details 2004-04-23 08:43 Record Lock details Denis P Gohel <sqllist@coralindia.com> @ 2004-04-23 10:03 ` Peter Eisentraut <peter_e@gmx.net> 0 siblings, 0 replies; 2+ messages in thread From: Peter Eisentraut @ 2004-04-23 10:03 UTC (permalink / raw) To: Denis P Gohel <sqllist@coralindia.com>; pgsql-sql Am Freitag, 23. April 2004 10:43 schrieb Denis P Gohel: > Is there a data dictionary in Postgres from where i can get the info about > locked rows of any table ? If possible the value of those locked record ? No, this information is not available for end users. > I have an ODBC application working on Postgres. There are Master child > tables. I want, if a user A is editing any document ( one master and set of > child records) in front-end application, the same should not be available > to other user for editing. > > I thought of using SELECT FOR UPDATE. But, in my case, i need to display > the name of application user and other details about the locked row. Keeping in mind that long-running transactions are not a good idea anyway, you should probably consider a user-space cooperative locking model. There is something in contrib/userlock, but I'm not sure whether that fits what you need. ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2004-04-23 10:03 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2004-04-23 08:43 Record Lock details Denis P Gohel <sqllist@coralindia.com> 2004-04-23 10:03 ` Peter Eisentraut <peter_e@gmx.net>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox