Re: [GENERAL] Killing a session

Even better. Thanks =). On Sat, 21 Aug 2004 20:14:53 -0400, Tom Lane <[EMAIL PROTECTED]> wrote: > > > Vitaly Belman <[EMAIL PROTECTED]> writes: > > Is there a way to kill a session in PostrgeSQL? I ran a bad query by > > mistake and I don't want to shut the whole database just to quit using > >

Re: [GENERAL] Few questions on postgresql (dblink, 2pc, clustering)

Jim Worke wrote: > Hi list, > > My boss would like to convert from MySQL to PostgreSQL, but there are a few > things that hold us back. > > We'd like to have the databases in several physical servers, with referential > integrity between the tables. Reading from Oracle articles, their > refer

[GENERAL] Few questions on postgresql (dblink, 2pc, clustering)

Hi list, My boss would like to convert from MySQL to PostgreSQL, but there are a few things that hold us back. We'd like to have the databases in several physical servers, with referential integrity between the tables. Reading from Oracle articles, their referential integrity can be done usin

Re: [GENERAL] Killing a session

Vitaly Belman <[EMAIL PROTECTED]> writes: > Is there a way to kill a session in PostrgeSQL? I ran a bad query by > mistake and I don't want to shut the whole database just to quit using > the whole CPU. ISTM what you really want is query cancel, not whole-session kill. Try "kill -INT ".

Re: [GENERAL] Killing a session

kill -15 pid# will kill a given thread ... you can look in the pg_stat_activity; the query_start shows when it started, the current_query shows at least a portion of the SQL the thread is executing, and procpid if the pid of the process to kill with a -15 command. Not sure about Windows varian

Re: libpq: passwords WAS: [GENERAL] scripting & psql issues

Hi Tom, Thanks a lot, that was the kind of clarification I needed. On Fri, Aug 20, 2004 at 10:32:59AM -0400, Tom Lane wrote: > Daniel Martini <[EMAIL PROTECTED]> writes: > > No he can't: > > Only if he is able to install a program on the webserver to > > actually login with a hashed password. If

[GENERAL] Killing a session

Is there a way to kill a session in PostrgeSQL? I ran a bad query by mistake and I don't want to shut the whole database just to quit using the whole CPU. -- ICQ: 1912453 AIM: VitalyB1984 MSN: [EMAIL PROTECTED] Yahoo!: VitalyBe ---(end of broadcast)---

Re: [GENERAL] ERROR: duplicate key violates unique constraint "pg_class_oid_index"

"borajetta" <[EMAIL PROTECTED]> writes: > I tried to cluster the isbn_table > cluster isbn_index_code on isbn_table; > ERROR: duplicate key violates unique constraint "pg_class_oid_index" Is this repeatable? If so, could you get a debugger stack trace from the point of the error? Also, exactl