Am Dienstag, 27. Juni 2006 15:47 schrieb Tom Lane:
> Thomas Mack <[EMAIL PROTECTED]> writes:
> > Am Montag, 26. Juni 2006 22:15 schrieb Tom Lane:
> >> What platform is that? If it's Solaris, see our doc/FAQ_Solaris
> >> about getting more useful info from "ps".
> >
> > Yes, it's Solaris 10. Lookin
Thomas Mack <[EMAIL PROTECTED]> writes:
> Am Montag, 26. Juni 2006 22:15 schrieb Tom Lane:
>> What platform is that? If it's Solaris, see our doc/FAQ_Solaris about
>> getting more useful info from "ps".
>>
> Yes, it's Solaris 10. Looking at
> http://www.postgresql.org/docs/faqs.FAQ_Solaris.html ,
Am Montag, 26. Juni 2006 22:15 schrieb Tom Lane:
> [EMAIL PROTECTED] writes:
> > I don't have a pg_stat_activity on this 7.4.6, so using ps gives me:
> >
> > [EMAIL PROTECTED] ~ 4 > ps -ef | grep postmaster
> > postgres 4499 4498 0 08:59:18 ? 0:04
> > /usr/local/pgsql/bin/postmaster -
[EMAIL PROTECTED] writes:
> I don't have a pg_stat_activity on this 7.4.6, so using ps gives me:
> [EMAIL PROTECTED] ~ 4 > ps -ef | grep postmaster
> postgres 4499 4498 0 08:59:18 ? 0:04
> /usr/local/pgsql/bin/postmaster -i -p 5356 -o -e
What platform is that? If it's Solaris, see
>Thomas Mack <[EMAIL PROTECTED]> writes:
>> Is there any chance to monitor the current transactions and abort them,
>> in case of need?
>
>Sure, just SIGINT whichever backend you want to cancel its query.
>Use "ps" or pg_stat_activity to figure out the right PID to kill.
>
I don't have a pg_stat_ac
Thomas Mack <[EMAIL PROTECTED]> writes:
> Is there any chance to monitor the current transactions and abort them,
> in case of need?
Sure, just SIGINT whichever backend you want to cancel its query.
Use "ps" or pg_stat_activity to figure out the right PID to kill.
regards,
Hi,
we use postgres for student's education and others.
Now we had an issue with some SQL statement in connection with some
triggers, that probably caused an infinite loop in processing for at
least 10 hours or so on some two to ten line tables.
Unfortunately, the students used the phpPgAdmin we
