Re: Putting code in main of src/backend/main/main.c

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "S -" <nat_lazy(at)hotmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Putting code in main of src/backend/main/main.c
Date: 2003-04-24 13:02:42
Message-ID: 12874.1051189362@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"S -" <nat_lazy(at)hotmail(dot)com> writes:
> We are working on a project where we want to create a single linked list
> that holds information of all the locks taken or being waited for by
> transactions in Postgresql.

How will you maintain such a list, when the underlying state is
constantly being changed by many different processes?

Perhaps more to the point, why would you want to? The existing lock
status data structures in shared memory can be traversed at need.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-04-24 13:03:57 Re: forking child processes in src/backend/main/main.c
Previous Message Ben Clewett 2003-04-24 12:49:57 Unrelated question