Tyson Oswald <[EMAIL PROTECTED]> writes:
> I just recently upgraded my Linux kernel to
> 2.4.8-34mdk, and now I cannot connect to postgresql
> through psql or pgaccess. I receive the following
> error apon the service starting up.
> pg_ctl: Another postmaster may be running. Trying to
> start p
I tried to send this message once, I think it didn't make it to the board.
I'm a new postgresql user, and I'm quite thrilled with it so far. However,
before I use it in any serious capacity, I would like to practice disaster
recovery and general administration procedures before I get myself in to
On Sun, 27 Jan 2002, Tyson Oswald wrote:
> Date: Sun, 27 Jan 2002 16:30:03 -0800 (PST)
> From: Tyson Oswald <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: [ADMIN] postmaster problem
>
> I just recently upgraded my Linux kernel to
> 2.4.8-34mdk, and now I cannot connect to postgresql
> thr
I just recently upgraded my Linux kernel to
2.4.8-34mdk, and now I cannot connect to postgresql
through psql or pgaccess. I receive the following
error apon the service starting up.
pg_ctl: Another postmaster may be running. Trying to
start postmaster anyway.
This happend apon bootup and also
> > We have a fresh database and have begun to observe performance
> > degradation for INSERTs as a table went from empty to 100,000-ish
> > rows. Initial INSERTs were sub second while after 30k rows, they
> > were 1-3 seconds.
>
> we just hit this problem when moving old database to new one (ne
On Sat, Jan 26, 2002 at 08:10:19PM -0600, Marc Mitchell wrote:
> We have a fresh database and have begun to observe performance degradation
> for INSERTs as a table went from empty to 100,000-ish rows. Initial
> INSERTs were sub second while after 30k rows, they were 1-3 seconds.
we just hit thi
