Stephan Szabo <[EMAIL PROTECTED]> writes:
> It's not really any different than other errors. The commit doesn't
> complain (although it also doesn't actually commit anything).
People have occasionally suggested that the command tag from a COMMIT
should read "ABORT" or "ROLLBACK" if the transaction
You can also get pid information from the system view pg_stat_activity,
which also tells you who your killing and what database they're
connected to.
On Jan 29, 2004, at 5:36 PM, Juan Miguel wrote:
You can kill the procs (connections) using kill -9 PID
For example,
ps aux | grep post
gives y
On Fri, 30 Jan 2004, Gaetano Mendola wrote:
> Hi all,
> is it normal that postgres dont complain
> doing a commit after a deadlock ?
>
> kalman=# select * from test where a = 5 for update;
> ERROR: deadlock detected
> DETAIL: Process 4144 waits for ShareLock on transaction 40180; blocked
> by p
We recently had an incident where a linux box went down with
a kernel error. A process on the box had an open connection
to a postgres session, and was in a transaction.
This situation was noticed when other processes connected to
postgres would not respond.
We observed that there was postmaster c
Hi all,
is it normal that postgres dont complain
doing a commit after a deadlock ?
kalman=# select * from test where a = 5 for update;
ERROR: deadlock detected
DETAIL: Process 4144 waits for ShareLock on transaction 40180; blocked
by process 4141.
Process 4141 waits for ShareLock on transaction
On Thu, 29 Jan 2004, Juan Miguel wrote:
> You can kill the procs (connections) using kill -9 PID
Just use kill PID first!
'kill -9' PID will force all backends to flush cache for no good reason.
Note that on most unixes, a plain kill PID will send the term signal,
which tells the process to po
The short answer is, you can run it on just about anything any system
that will run an OS it will run under.
How well it will perform depends on your system and what you're trying
to do with it.
On Thu, 29 Jan 2004, Juan Carlos Diez wrote:
> Hello, I'm evaluating that version and I can't find sy
You can kill the procs (connections) using kill -9 PID
For example,
ps aux | grep post
gives you a list of the postgres processes (all the active connections,
and main postmaster). Here you can see the IP of the manchines connected
from.
Therefore, its easy to create an shell script for killin
It's possible to get process ids for clients using something like ps
-ef | grep postgres. I wonder, is it safe to use kill to terminate
those threads? If this doesn't mess up the database, it might work.
Hadley Willan wrote:
Thanks for that, however that's quite heavy handed in that it
Thanks for that, however that's quite heavy handed in that it will stop the postgres instance.
Is there any way to close connections to a database without stopping postgres itself?
E.G I have three databases, A,B and C, and only want to close C.
Thanks
On Fri, 2004-01-30 at 10:21, Gregory
pg_ctl stop[-W] [-D DATADIR] [-s] [-m SHUTDOWN-MODE]
e.g.
pg_ctl stop -D /data/postgres/gex_runtime -m fast
will shut down all connections and stop the postgres instance:
Shutdown modes are:
smart quit after all clients have disconnected
fastquit directly, with proper shu
Hello,
How do I force postmaster to terminate active connections on other databases?
Thanks
--
Hadley Willan » Director » [EMAIL PROTECTED] » +64(21) 28 41 463
Deeper Design Limited » +64(7) 377 3328 » www.deeperdesign.com
Hello, I'm evaluating that version and I can't find system requirements for it. Could
anybody please help me with these questions?
1.1. Hardware:
1.1.1. C.P.U. (how many processors, what speed)
1.1.2. Ram. (minimum and desired)
1.1.3. Disk.
1.1.4. Networking.
1.1.5. Scalability
1.2. Software:
1
hello tony,
Our tool DeZign for Databases can do this for you. With the ImportER
Scripts add-on you can import SQL scripts containing create table
statements etc into the data modeling tool DeZign for Databases.
more info at
http://www.datanamic.com
regards
rick
[EMAIL PROTECTED] (Tony Reina) w
Hi,
I have Two databases names 'MyDb1' and 'MyDb2' in My
System.
I have installed Postgres 7.4 with dblink
What i need is, when ever a NEW record is inserted in
'MyDb1' , i want fire a Trigger or Rule to insert the
Same Record to MyDb2 database.
I am Using MAC OS 10.2
Anybody Got Idea how to d
Nothing is generated to the screen and the log file is redirected to
stderr.
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 29, 2004 9:16 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [ADMIN] Error seen when vacuuming pg_largeobject tabl
"Chris White \(cjwhite\)" <[EMAIL PROTECTED]> writes:
> Sorry I meant to say the server terminated the connection as indicated
> by the error message but the server is still running and there is no
> core (This time I enabled them).
Hard to believe there's no core. What shows up in the postmaster
Rich Cullingford <[EMAIL PROTECTED]> writes:
> In trying to write a utility to drop/restore table indexes (as an aid to
> a fast reload of the associated tables), I ran into the definition of
> the field pg_index.indkey as an int2vector.
> How can I deal with this type in plpgsql?
You should be
Sorry I meant to say the server terminated the connection as indicated
by the error message but the server is still running and there is no
core (This time I enabled them).
Chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane
Sent: Thursday, Jan
"Iain" <[EMAIL PROTECTED]> writes:
> If we use it, can we stop using nightly vacuums? I'd like to do this if
> possible, since the current version (it's a 7.1 db) of the system runs a
> number of batch processes at night (large deletes and large inserts), and
> finishes with a vacuum analyse. The v
Hello, all.
In trying to write a utility to drop/restore table indexes (as an aid to
a fast reload of the associated tables), I ran into the definition of
the field pg_index.indkey as an int2vector. I can't see any place in the
doc that says what to do with this type, you can't cast it to any a
"Chris White \(cjwhite\)" <[EMAIL PROTECTED]> writes:
> It happened again. After doing the reindex, I did a vacuum full on the
> pg_largeobject table. This time I did not get the TUPLE INDEX error but
> the server terminated at the end of the vacuum command.
Can you enable core dumps and get a sta
--- Tom Lane <[EMAIL PROTECTED]> wrote:
> Frank Way <[EMAIL PROTECTED]> writes:
> > After finding the ctid in (block,tuple) format, how do you know
> which
> > file in all the subdirectories under /usr/local/pgsql/data/base
> > contains that block?
>
> The subdirectories are named after the OIDs
Thanks for the article. It did help some but I am still not sure if
representing a tree is best served using a self referential table.
Wouldn't it be better to separate it into several tables?
Can anyone else comment? Anyone have experience storing data that is
hierarchical in nature (e.g. a tr
On Thu, Jan 29, 2004 at 18:59:28 +0900,
Iain <[EMAIL PROTECTED]> wrote:
I haven't used auto_vacuum, but I seen comments on the lists indicating
that it works OK.
> If I start a VACUUM FULL, is it ok to interrupt it part way through? I mean,
> is a partially completed vacuum full worth anything
(B
(B
(BHi All,
(B
(BI'm supposed to put together a plan for
(Bthe routine maintenance of the new database we are building using v7.4, and I
(Bhave a question or two.
(B
(BI'm interested in the auto vacuum daemon,
(Bbut havn't located any good information about it so far, I'd like t
26 matches
Mail list logo
