From: | Brian McCane <bmccane(at)mccons(dot)net> |
---|---|
To: | Markus Wollny <Markus(dot)Wollny(at)computec(dot)de> |
Cc: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: postmaster shutdown |
Date: | 2002-03-13 17:58:36 |
Message-ID: | 20020313115349.T51882-100000@fw.mccons.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Don't know if this applies when using cygwin or not, but...
I was getting the same basic error whenever I tried to fire up a trigger
that used plpgsql language functions. It turns out that when FreeBSD
created their new port, they left the old plpgsql.so on the drive, and put
the new one in a different place. This was only a problem when I used
pg_dump to create a backup of a 7.1.3 to 7.2. The dump explicitly named
the directory that had the old plpgsql.so, so I had a 7.2 postmaster and a
7.1.3 plpgsql.so.
Anyway, long story short. Every timed it fired off a trigger, the
postmaster core dumped. I finally saw an offhand comment by someone in
this group, searched /usr/local and found both files. I then deleted the
old one, and dropped the language and re-added. Now everything is
cruising right along.
- brian
On Wed, 6 Mar 2002, Markus Wollny wrote:
> This behaviour is starting to get on my nerves...
>
> Could somebody give me a hint as to what exactly happened here and how I
> can avoid it in the future?
>
> This is the relevant bit of the Logfile:
> ----------------snip----------------
> 2002-03-06 16:02:52 FATAL 1: Database "template0" is not currently
> accepting connections
> 2002-03-06 16:02:53 FATAL 1: Database "template0" is not currently
> accepting connections
> 2002-03-06 16:02:53 FATAL 1: LWLockAcquire: can't wait without a PROC
> structure
> 2002-03-06 16:02:53 DEBUG: server process (pid 1848) exited with exit
> code 1
> 2002-03-06 16:02:53 DEBUG: terminating any other active server
> processes
> 2002-03-06 16:02:53 NOTICE: Message from PostgreSQL backend:
> The Postmaster has informed me that some other backend
> died abnormally and possibly corrupted shared memory.
> I have rolled back the current transaction and am
> going to terminate your database system connection and exit.
> Please reconnect to the database system and repeat your query.
> [this message is repeated six times]
> 2002-03-06 16:02:56 DEBUG: all server processes terminated;
> reinitializing shared memory and semaphores
> IpcMemoryCreate: shmget(key=5432001, size=2039808, 03600) failed: Not
> enough memory
>
> This error usually means that PostgreSQL's request for a shared
> memory segment exceeded available memory or swap space.
> To reduce the request size (currently 2039808 bytes), reduce
> PostgreSQL's shared_buffers parameter (currently 128) and/or
> its max_connections parameter (currently 32).
>
> The PostgreSQL Administrator's Guide contains more information about
> shared memory configuration. [that wasn't really too helpful on this
> matter; next I started up the service again. The subsequent entires go
> along as follows:]
>
> 2002-03-06 16:15:25 DEBUG: database system was interrupted at
> 2002-03-06 15:58:24
> 2002-03-06 16:15:25 DEBUG: checkpoint record is at 1/E3952A78
> 2002-03-06 16:15:25 DEBUG: redo record is at 1/E3952A78; undo record is
> at 0/0; shutdown FALSE
> 2002-03-06 16:15:25 DEBUG: next transaction id: 8343789; next oid:
> 2876559
> 2002-03-06 16:15:25 DEBUG: database system was not properly shut down;
> automatic recovery in progress
> 2002-03-06 16:15:25 DEBUG: redo starts at 1/E3952AB8
> 2002-03-06 16:15:25 DEBUG: ReadRecord: record with zero length at
> 1/E39594F8
> 2002-03-06 16:15:25 DEBUG: redo done at 1/E39594D0
> 2002-03-06 16:15:27 DEBUG: database system is ready
> ----------------snip----------------
>
> I have absolutely no idea what I should do about this. Most of the time
> the thing is running fine, but it just quits occasionally. It's
> PostgreSQL 7.2 running on Cygwin, Win2k, 2GB RAM, quad-processor by the
> way, we are doing access via ODBC. I'd be happy to provide any more
> information if it could help in solving the problem - and I'd be very
> happy about helpful advice.
>
> Thanks in advance,
>
> Markus
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
>
Wm. Brian McCane | Life is full of doors that won't open
Search http://recall.maxbaud.net/ | when you knock, equally spaced amid those
Usenet http://freenews.maxbaud.net/ | that open when you don't want them to.
Auction http://www.sellit-here.com/ | - Roger Zelazny "Blood of Amber"
From | Date | Subject | |
---|---|---|---|
Next Message | Herb Blacker | 2002-03-13 19:21:00 | Multi-threading |
Previous Message | Joo Carlos Fernandes Costa | 2002-03-13 17:46:21 |