Re: [ADMIN] problems doing sub-selects on PostgreSQL 7.1.3 and Solaris 7

[Heather Johnson]

Hi Tom--

 

Sure, this is what I get:

 

2001-12-11 09:40:24 DEBUG:  StartTransactionCommand
2001-12-11 09:40:24 DEBUG:  query: select count(*) from users where id not in (select users_id from users_demographics)
/opt/postgres/bin/postmaster: reaping dead processes...
/opt/postgres/bin/postmaster: CleanupProc: pid 26260 exited with status 0

 

The E-450 box is managed by someone other than myself, but I've asked the person primarily responsible for managing it about quotas and other externally imposed resource limits. He doesn't think that there are any.

 

Heather

 

 

----- Original Message -----

From: "Tom Lane" <[EMAIL PROTECTED]>

To: "Heather Johnson" <[EMAIL PROTECTED]>

Cc: <[EMAIL PROTECTED]>; "Harry Ford" <[EMAIL PROTECTED]>; "Serge Canizares" <[EMAIL PROTECTED]>; "Marie Musacchio" <[EMAIL PROTECTED]>

Sent: Monday, December 10, 2001 5:34 PM

Subject: Re: [ADMIN] problems doing sub-selects on PostgreSQL 7.1.3 and Solaris 7

> "Heather Johnson" <[EMAIL PROTECTED]> writes:
> > I have been having trouble getting subselect queries to complete on a Sun E=
> > -450 running Solaris 7 and PostgreSQL 7.1.3. Just about any subselect query=
> >  I try to run will fail to complete execution---Postgres's serverlog indica=
> > tes that the process associated with the query gets killed after a few minu=
> > tes have gone by.
>
> Could we see the exact text of the log entries?
>
> Is it possible that you have some kernel limit on CPU time, memory
> space, etc expended by any one backend process?
>
> regards, tom lane