On 11/8/05, Andrew Watters <[EMAIL PROTECTED]> wrote:
I am trying to find details about open connections. I can see that thereare open connections through Tools | Server Status in pgAdmin III. Howcan I find what the current and/or last SQL statement was that was run
in those open connections please
I was interested in getting feedback from current mail group users.We have mirrored your mail list in a new application that provides a more aggregated and safe environment which utilizes the power of broadband.Roomity.com v 1.5 is a web 2.01 community webapp. Our newest version adds broadcast vide
On Tuesday 08 November 2005 05:10, Lane Van Ingen wrote:
> What does the 'c' part of the -tc command do? It is not documented
> in any information I have.
Show tuples only (per psql --help)
Cheers,
Steve
---(end of broadcast)---
TIP 2: Don't 'kill
psql -c COMMAND DATABASE
executes COMMAND using DATABASE and displays the results without
starting psql interactively.
Regards,
Eric Faulhaber
Lane Van Ingen wrote:
What does the 'c' part of the -tc command do? It is not documented in
any information I have.
-Original Message-
From
Same as -t -c...
On Tue, Nov 08, 2005 at 08:10:28AM -0500, Lane Van Ingen wrote:
> What does the 'c' part of the -tc command do? It is not documented in
> any information I have.
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Jim C. Nasby
> Sent: Mo
On Tue, 2005-11-08 at 13:29 -0500, Tom Lane wrote:
> Joost Kraaijeveld <[EMAIL PROTECTED]> writes:
> > Panoramix:/var/lib/postgresql/8.0/main# ls /opt/ -al
> > total 56
> > drwxrwxrw- 14 root staff.
>^
> > drwxr-xr-x 22 root root ..
> > drwx-- 3 postgres postgres
On Tue, 8 Nov 2005, Joost Kraaijeveld wrote:
Panoramix:/var/lib/postgresql/8.0/main# ls /opt/pg_xlog/ -al
total 295284
drwx-- 3 postgres postgres .
drwxrwxrw- 14 root staff..
-rw--- 1 postgres postgres 0001003300B4
-rw--- 1 postgres postgres 0001003
Joost Kraaijeveld <[EMAIL PROTECTED]> writes:
> Panoramix:/var/lib/postgresql/8.0/main# ls /opt/ -al
> total 56
> drwxrwxrw- 14 root staff.
^
> drwxr-xr-x 22 root root ..
> drwx-- 3 postgres postgres pg_xlog
There's your problem --- postgres can't do lookups in /
Joost Kraaijeveld wrote:
> lrwxrwxrwx 1 root root pg_xlog -> /opt/pg_xlog
Maybe this one here? Try chown'ing it to postgres:postgres and see what happens
--
___
This e-mail may be privileged and/or confidential, and the sender does
not waive any related ri
Hi Tom,
On Tue, 2005-11-08 at 13:05 -0500, Tom Lane wrote:
> Joost Kraaijeveld <[EMAIL PROTECTED]> writes:
> >>> PANIC: could not open file
> >>> "/var/lib/postgresql/8.0/main/pg_xlog/0001.history": Permission
> >>> denied
>
> >> So what happens if you do:
> >> ls -l /var/lib/postgresql/8.0/
Joost Kraaijeveld <[EMAIL PROTECTED]> writes:
>>> PANIC: could not open file
>>> "/var/lib/postgresql/8.0/main/pg_xlog/0001.history": Permission
>>> denied
>> So what happens if you do:
>> ls -l /var/lib/postgresql/8.0/main/pg_xlog/0001.history
> There is not a file with that name.
Not
Hi Jeff,
On Tue, 2005-11-08 at 09:11 -0800, Jeff Frost wrote:
> On Tue, 8 Nov 2005, Joost Kraaijeveld wrote:
>
> >> Joost Kraaijeveld <[EMAIL PROTECTED]> writes:
> >>> PANIC: could not open file
> >>> "/var/lib/postgresql/8.0/main/pg_xlog/0001.history": Permission
> >>> denied
>
> So what h
Dan,
Sure, just bring it up in a different directory and have it listen on a
different port. You could either dump/restore to get the data over to it or
use a replication tool such as slony or mammoth to do the deed. The latter
method has the benefit of keeping it up to date while you poke a
you only need make postgres 8.1.0 run using another port, example 5438
2005/11/8, Dan The Man <[EMAIL PROTECTED]>:
> Hi,
> I have enough resources on my 3 postgresql servers to run more than one
> instance of postgres. Is there a way to keep my production db up and
> running in 8.0.3 while I also
On Tue, 8 Nov 2005, Joost Kraaijeveld wrote:
Joost Kraaijeveld <[EMAIL PROTECTED]> writes:
PANIC: could not open file
"/var/lib/postgresql/8.0/main/pg_xlog/0001.history": Permission
denied
So what happens if you do:
ls -l /var/lib/postgresql/8.0/main/pg_xlog/0001.history
Can you po
Hi,
I have enough resources on my 3 postgresql servers to run more than one
instance of postgres. Is there a way to keep my production db up and
running in 8.0.3 while I also run 8.1.0 on the same server? Then, I could
copy the data and support two databases until things looked good. Then,
On Tue, 2005-11-08 at 10:59 -0500, Tom Lane wrote:
> Seems *highly* unlikely, though I suppose you could ask the Debian
> maintainer what he changed between -7 and -15.
I have triple checked, I even let someone else do the same procedure but
history repeats itself. It does not work. I have send the
What does the 'c' part of the -tc command do? It is not documented in
any information I have.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Jim C. Nasby
Sent: Monday, November 07, 2005 5:38 PM
To: Chris Hoover
Cc: pgsql-admin@postgresql.org
Subject: Re: [AD
"Joost Kraaijeveld" <[EMAIL PROTECTED]> writes:
> I checked all this with another Debian box which has a slightly other
> PostgreSQL version and there it works as advertised. So PostgreSQL
> 8.0.3-7 works with symlinked pg_xlog directory and PostgreSQL 8.0.3-15
> does not.
Seems *highly* unlikely,
I just tried to install 8.1 from the rpms provided on the postgresql.org mirrors.
I had 8.0 installed, and removed all the 8.0 rpms. I then blew
away my 8.0 cluster (playing with a test server, obviously). When
I recreated the directory for the cluster and tried to run initdb,
initdb abended wit
Hi Tom,
> Joost Kraaijeveld <[EMAIL PROTECTED]> writes:
> > PANIC: could not open file
> > "/var/lib/postgresql/8.0/main/pg_xlog/0001.history": Permission
> > denied
>
> Read the error message! You have a permissions problem ---
> most likely,
> some directory in the path to the new xlog d
Hi
I am trying to find details about open connections. I can see that there
are open connections through Tools | Server Status in pgAdmin III. How
can I find what the current and/or last SQL statement was that was run
in those open connections please?
Thanks for your help
Andrew
--
Joost Kraaijeveld <[EMAIL PROTECTED]> writes:
> PANIC: could not open file
> "/var/lib/postgresql/8.0/main/pg_xlog/0001.history": Permission
> denied
Read the error message! You have a permissions problem --- most likely,
some directory in the path to the new xlog directory isn't readable by
Joost Kraaijeveld wrote:
> On Mon, 2005-11-07 at 23:46 -0800, Jeff Frost wrote:
>> So, what happens if you do this as the postgres user:
>> ls -l /var/lib/postgresql/8.0/main/pg_xlog/
>> I'm going to guess the output indicates you have a directory inside
>> pg_xlog called pg_xlog_orig.
> Sorry, cop
We’re having problems restoring a database, we
dumped and tried to restore on the same databaseserver., and used the command:
pg_dump -Ft -b {dbname} > {filename}
to dump the database and
pg_restore -d {dbname} {filename}
to restore the database. At some point we’re
gettin
On Mon, 2005-11-07 at 23:46 -0800, Jeff Frost wrote:
> So, what happens if you do this as the postgres user:
>
> ls -l /var/lib/postgresql/8.0/main/pg_xlog/
>
> I'm going to guess the output indicates you have a directory inside pg_xlog
> called pg_xlog_orig.
Sorry, copied and pasted the wrong p
26 matches
Mail list logo
