Re: Query cancelled errors

Could we try 'screen' maybe and see if it persists?

'screen' - detatch and re-attach to a terminal
http://www.math.fu-berlin.de/~guckes/screen/

> -----Original Message-----
> From: pgsql-novice-owner(at)postgresql(dot)org
> [mailto:pgsql-novice-owner(at)postgresql(dot)org]On Behalf Of Tom Lane
> Sent: Tuesday, September 16, 2003 3:26 PM
> To: David Rickard
> Cc: pgsql-novice(at)postgresql(dot)org
> Subject: Re: [NOVICE] Query cancelled errors
>
>
> David Rickard <David(dot)Rickard(at)GTScompanies(dot)com> writes:
> >>> ERROR: Query was cancelled.
> >>
> >> Something is sending the backend a SIGINT. What platform are you on?
> >> (For that matter, what PG version are you using?)
>
> > System: SunOS rutabaga 5.9 Generic_112233-07 sun4u sparc SUNW,Ultra-250
> > PG: 7.3.4
>
> A bit of googling turned up this:
> http://dbforums.com/arch/128/2002/7/425070
>
> which suggests that the solution is to not use /sbin/sh as your root
> shell; or perhaps better, arrange to spawn Postgres from a startup
> script rather than manually from a root shell.
>
> Judging from that discussion, my idea of interposing nohup won't help.
> I had thought that maybe nohup would dissociate Postgres from the
> root shell's process group, but evidently it doesn't do that on Solaris.
> (I can't find any evidence that it does so on Linux or HPUX, either,
> so I'm not going to modify the standard version of pg_ctl, unless
> someone comes up with evidence that it would help somewhere.)
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
>