Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
dirty select
- From: Sim Zacks <sim(at)compulab(dot)co(dot)il>
- To: pgsql-general(at)postgresql(dot)org
- Subject: dirty select
- Date: Tue, 08 Apr 2008 14:39:32 +0300
- Message-id: <ftflhi$1fjd$1(at)news(dot)hub(dot)org>
Is there any way to do a dirty select to find out what a process is up to? I have a process that is writing 150,000 rows to a table and it is taking way longer then I thought it would. I would like to read the table to make sure that it is not looping through the data or anything like that. Thank you SIm
- Follow-Ups:
- Re: dirty select
- From: Andrew Sullivan
- Re: dirty select
- Prev by Date: Re: "too many trigger records found for relation xyz"
- Next by Date: Re: select distinct and index usage
- Previous by thread: High Availability / Replication with Sequoia
- Next by thread: Re: dirty select
- Indexes: