Re: [ADMIN] postmaster is restarting

ro you've >> installed, etc... >> >> >> - Original Message - >> From: Rodrigo Barboza >> To: pgsql-admin@postgresql.org >> Sent: Mon, 29 Apr 2013 21:35:08 - (UTC) >> Subject: [ADMIN] postmaster is restarting >> >> Hi, guys. >

Re: [ADMIN] postmaster is restarting

rom: Rodrigo Barboza > To: pgsql-admin@postgresql.org > Sent: Mon, 29 Apr 2013 21:35:08 - (UTC) > Subject: [ADMIN] postmaster is restarting > > Hi, guys. > I am using the script that comes with postgres installation to start and > stop my database. > When I stop the

Re: [ADMIN] postmaster is restarting

You probably have a service with overarching control over PostgreSQL. Gonna depend on how you installed PostgreSQL, which distro you've installed, etc... - Original Message - From: Rodrigo Barboza To: pgsql-admin@postgresql.org Sent: Mon, 29 Apr 2013 21:35:08 - (UTC) Subject: [

Re: [ADMIN] postmaster is restarting

On Mon, Apr 29, 2013 at 2:35 PM, Rodrigo Barboza wrote: > Hi, guys. > I am using the script that comes with postgres installation to start and > stop my database. > When I stop the database, it restarts after some minutes. > I have looked through every path and I don't find who starts it again. >

[ADMIN] postmaster is restarting

Hi, guys. I am using the script that comes with postgres installation to start and stop my database. When I stop the database, it restarts after some minutes. I have looked through every path and I don't find who starts it again. I am using Linux. Is there some kind of signaling to for it to restar

Re: [ADMIN] Postmaster taking up 100% of CPU

higeon wrote: The following is my top log and ps log: Try using "top -c" on Linux instead. Then you'll be able to see what all the processes are doing. Any heavy query will cause a CPU to consume 100% of its time when running, so there may be nothing wrong other than you have queries to op

[ADMIN] Postmaster taking up 100% of CPU

Hi,everyone The CPU of my linux box is 100% by postmaster processes for hours. How to deal with it? The following is my top log and ps log: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 8970 postgres 16 0 53692 36m 34m R 27.3 3.6 1:14.80 postmaster 8807 postgres

Re: [ADMIN] postmaster -D PGDATA and postmaster.pid

Thanks Tom..that did the magic Would I allow PG to start from any -D place by saying semange fcontext -a -t postgresql_db_t "/qmsvol(/.*)?" Thanks Medi On Nov 26, 2007 7:48 PM, Tom Lane <[EMAIL PROTECTED]> wrote: > "Medi Montaseri" <[EMAIL PROTECTED]> writes: > > However if I try to start

Re: [ADMIN] postmaster -D PGDATA and postmaster.pid

"Medi Montaseri" <[EMAIL PROTECTED]> writes: > However if I try to start the engine with "/etc/init.d/postgresql start " or > service postgresql start" I see the following error message in my PGLOG (ie > /var/log/pgsql/pgstartup.log) > postmaster cannot access the server configuration file > "/qms

[ADMIN] postmaster -D PGDATA and postmaster.pid

Hi, I am configuring a PG 8.1.9 on CentOS 5. I am seeing some anomalies and would like you feedback. I have defined a new PGDATA=/qmsvol/pg_8.1.9/data, ran initdb -D /qmsvol/pg_8.1.9/data successfully and can start the engine with pg_ctl -D $PGDATA. I have also populated /etc/sysconfig/pgsql/post

Re: [ADMIN] Postmaster Question

[EMAIL PROTECTED] writes: > How can I stop postmaster when it is in an uncontrollable state? If I > cannot simply stop it by stopping the service (net stop), and I can't get > to it through psql, what is the easiest way to stop it? This question is too open-ended to have any simple answer. Ple

[ADMIN] Postmaster Question

How can I stop postmaster when it is in an uncontrollable state? If I cannot simply stop it by stopping the service (net stop), and I can't get to it through psql, what is the easiest way to stop it? Thanks, Patrick The information contained in this communication is confidential, it is inte

Re: [ADMIN] postmaster restart on a different dataDir

Actually I found the answerpg_ctl supports a -w switch which waits for the start operation to complete. Decibel...without -w, pg_ctl will return immediately before postmaster is fully operational. If you don't believe me start the engine and try to connect to it right away with pgsql(1)... Ch

Re: [ADMIN] postmaster restart on a different dataDir

On Mon, Aug 13, 2007 at 04:05:37PM -0700, Medi Montaseri wrote: > Hi, > > I am trying to measure startup time of postmaster. Say I have postmaster Why? > running on -D /tmp/d1 and would like to restart it on -D /tmp/d2. > > If I just say > time pg_ctl restart -D /tmp/d2 > it will not produce an

[ADMIN] postmaster restart on a different dataDir

Hi, I am trying to measure startup time of postmaster. Say I have postmaster running on -D /tmp/d1 and would like to restart it on -D /tmp/d2. If I just say time pg_ctl restart -D /tmp/d2 it will not produce an accurate result because pg_ctl will start postmaster in the background and return imme

Re: [ADMIN] postmaster udp ports?

Andrew Zahn <[EMAIL PROTECTED]> writes: > Does anyone know what postmaster is doing with these UDP ports? Statistics collection. regards, tom lane ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster

[ADMIN] postmaster udp ports?

Does anyone know what postmaster is doing with these UDP ports? On a fresh installation these ports are opened and I cannot find any documentation on what they are for postmaste 5398 postgres3u IPv4 53988 TCP *:5432 (LISTEN) postmaste 5398 postgres5u IPv4 53994 UDP

Re: [ADMIN] Postmaster log perms and line suffix

my 2 cents 1 setup logcheck to send message to a public email box2 use apache to access log file themselfOn 5/1/06, Koen Martens < [EMAIL PROTECTED]> wrote:Chris Hoover wrote:> On 26 Apr 2006 12:39:26 -0400, *Jerry Sievers* < [EMAIL PROTECTED]> [EMAIL PROTECTED]>> wrote:>> Pgadmins, 2 loosly re

Re: [ADMIN] Postmaster log perms and line suffix

Chris Hoover wrote: > On 26 Apr 2006 12:39:26 -0400, *Jerry Sievers* <[EMAIL PROTECTED] > > wrote: > > Pgadmins, 2 loosly related questions > > 1. We have need to let developers view the postmaster logs on some of >our environments and wish NOT to give th

Re: [ADMIN] Postmaster log perms and line suffix

On 26 Apr 2006 12:39:26 -0400, Jerry Sievers <[EMAIL PROTECTED]> wrote: Pgadmins, 2 loosly related questions1. We have need to let developers view the postmaster logs on some of   our environments and wish NOT to give them access to the postgres   Unix acct if possible.  It looks though as if log f

[ADMIN] Postmaster log perms and line suffix

Pgadmins, 2 loosly related questions 1. We have need to let developers view the postmaster logs on some of our environments and wish NOT to give them access to the postgres Unix acct if possible. It looks though as if log file perms are determined by the global umask set in postmaster.c

Re: [ADMIN] Postmaster errors

Title: RE: [ADMIN] Postmaster errors Great, thank you for the additional info. Tim  -Original Message- From:   Michael Fuhr [mailto:[EMAIL PROTECTED]] Sent:   Thursday, February 02, 2006 1:05 PM To: mcelroy, tim Cc: 'pgsql-admin@postgresql.org' Subject:   

Re: [ADMIN] Postmaster errors

On Thu, Feb 02, 2006 at 12:34:44PM -0500, mcelroy, tim wrote: > That was it, a fellow admin is watching the postmaster with OpenNMS I think OpenNMS has a way to set up a custom poller that can do anything you want (e.g., connect to the database, issue a query, check the results). I was playin

Re: [ADMIN] Postmaster errors

Title: RE: [ADMIN] Postmaster errors That was it, a fellow admin is watching the postmaster with OpenNMS Thanks for the tip! Tim  -Original Message- From:   Michael Fuhr [mailto:[EMAIL PROTECTED]] Sent:   Thursday, February 02, 2006 11:10 AM To: mcelroy, tim Cc

Re: [ADMIN] Postmaster errors

On Thu, Feb 02, 2006 at 10:58:52AM -0500, mcelroy, tim wrote: > Has anyone encountered these errors? They repeat every five (5) minutes in > my log file. Is there something I may have set incorrectly in my > postgresql.conf file? Odd as I find them in my DEV & QA logs but not > Production >

[ADMIN] Postmaster errors

Title: Postmaster errors Good morning, Has anyone encountered these errors?  They repeat every five (5) minutes in my log file.  Is there something I may have set incorrectly in my postgresql.conf file?  Odd as I find them in my DEV & QA logs but not Production 2006-02-02 10:52:33 EST US

Re: [ADMIN] postmaster hangs

sorry ,but i had to go with my job so i have killed one of the backends and this made the post restart. However befor this i have done another backtrace ,the one that was hang in the middle of SELECT (not startup) and got this: #0 0xe410 in ?? () #1 0xbfffcf08 in ?? () #2 0x0001 in

Re: [ADMIN] postmaster hangs

Tsirkin Evgeny <[EMAIL PROTECTED]> writes: > Today i was trying to run an old ver. of an application on test server . > After a while i have got the pg hangs : It looks like someone is holding a critical LWLock --- hard to tell if it's the BufMgrLock or a per-buffer lock for a system index's metap

Re: [ADMIN] postmaster hangs

Forgot to mention this SUSE 9 with the default 2.6.5 kernel. Logs does not show anything strange and post refuses to shutdown gracefully or receive connections.Processes just hangs out there ... . Evgeny. On Wed, 4 Jan 2006, Tsirkin Evgeny wrote: > Today i was trying to run an old ver. of an app

[ADMIN] postmaster hangs

Today i was trying to run an old ver. of an application on test server . After a while i have got the pg hangs : 9899 ?S 0:00 postgres: [local] SELECT 9932 ?S 0:00 postgres: [local] SELECT 9933 ?S 0:00 postgres: [local] startup 9936 ?S 0:00 p

Re: [ADMIN] postmaster blues after system restart

"Thomas F. O'Connell" <[EMAIL PROTECTED]> writes: > Does postgres just use /tmp because it will generally be known to > exist and be writable? I suppose that was the original motivation. We've had repeated troubles over the years with using /tmp --- for example, the code now goes to considerabl

Re: [ADMIN] postmaster blues after system restart

On Tue, 2005-10-18 at 01:29 -0400, Tom Lane wrote: > "Thomas F. O'Connell" <[EMAIL PROTECTED]> writes: > > But cleaning out /tmp seems to be a part of institutional practice on > > Linux, > > I'm unconvinced of that. A quick test on Fedora Core 4 shows that > random files in /tmp survive reboot

Re: [ADMIN] postmaster blues after system restart

On Oct 18, 2005, at 12:29 AM, Tom Lane wrote: "Thomas F. O'Connell" <[EMAIL PROTECTED]> writes: But cleaning out /tmp seems to be a part of institutional practice on Linux, I'm unconvinced of that. A quick test on Fedora Core 4 shows that random files in /tmp survive reboot, and any moment

Re: [ADMIN] postmaster blues after system restart

"Thomas F. O'Connell" <[EMAIL PROTECTED]> writes: > But cleaning out /tmp seems to be a part of institutional practice on > Linux, I'm unconvinced of that. A quick test on Fedora Core 4 shows that random files in /tmp survive reboot, and any moment of thought would show why users would object t

Re: [ADMIN] postmaster blues after system restart

Well, after digging a bit deeper, I guess the conclusion is that the best practice is to trust package maintainers and follow their lead when installing from source. I notice, for instance, that contrib/start-scripts/linux recommends S98 for /etc/rc. That wouldn't've prevented the S99 mount

Re: [ADMIN] postmaster blues after system restart

On Fri, 2005-10-14 at 15:49, Thomas F. O'Connell wrote: The culprit that ended up leading to my original post was an NFS script that cleans out /tmp. It was running as the last thing in a given boot level, so it blew away the socket file in /tmp. I'm sure you already know this, but wildly / ra

Re: [ADMIN] postmaster blues after system restart

On Fri, 2005-10-14 at 15:49, Thomas F. O'Connell wrote: > The culprit that ended up leading to my original post was an NFS > script that cleans out /tmp. It was running as the last thing in a > given boot level, so it blew away the socket file in /tmp. I'm sure you already know this, but wildl

Re: [ADMIN] postmaster blues after system restart

The culprit that ended up leading to my original post was an NFS script that cleans out /tmp. It was running as the last thing in a given boot level, so it blew away the socket file in /tmp. Restarting postgres after boot recreated the file, so that explained the behavior discrepancy I was

Re: [ADMIN] postmaster blues after system restart

On Oct 13, 2005, at 9:35 PM, Tom Lane wrote: "Thomas F. O'Connell" <[EMAIL PROTECTED]> writes: When I restart, everything seems to come up fine with the exception that postmaster starts in a state such that it doesn't seem to be accepting connections (either over UNIX or TCP/IP). As best I ca

Re: [ADMIN] postmaster blues after system restart

"Thomas F. O'Connell" <[EMAIL PROTECTED]> writes: > When I restart, everything seems to come up fine with the exception > that postmaster starts in a state such that it doesn't seem to be > accepting connections (either over UNIX or TCP/IP). As best I can > tell, it is using the init script t

Re: [ADMIN] postmaster blues after system restart

On Thu, 13 Oct 2005, Thomas F. O'Connell wrote: The very odd thing is that if I use this same init script manually once the box is up to stop/start postgres, everything comes up roses. You could post your init script for us to look at, but my first question is this: Is postgresql actually run

[ADMIN] postmaster blues after system restart

I'm experiencing an unusual situation on a recently reprovisioned server. It's a Debian server (testing/unstable) running a 2.6.13.3 kernel. postgres 8.0.4 was built from source. I'm using a slightly modified version of the tarball sample init script that includes a function to start pg_a

[ADMIN] Postmaster

Hi Folks! What are the tasks of the postmaster process in 8.x? Is it only responsible to make the connections? And what about concurrent access and transaction management? Thanks. ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster

Re: [ADMIN] postmaster stop hangs

"Simpson" <[EMAIL PROTECTED]> writes: > Yes, it does it consistently. > Maybe I should start from scratch, if this seems very broken. It seems not only very broken, but practically impossible: there is only one routine that writes that file, and it definitely writes the result of getpid(), and i

Re: [ADMIN] postmaster stop hangs

Yes, it does it consistently. Maybe I should start from scratch, if this seems very broken. Drew. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Tom Lane Sent: Sunday, April 24, 2005 11:02 AM To: Simpson Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN

Re: [ADMIN] postmaster stop hangs

"Simpson" <[EMAIL PROTECTED]> writes: > Here is a ps of the currently running instance: > postgres 5671 1 0 02:32 pts/000:00:00 > /usr/local/pgsql/bin/postmaster -D /data/pgsql/data > postgres 5674 5671 0 02:32 pts/000:00:00 postgres: writer process > postgres 5675 5671 0 02:32

[ADMIN] postmaster stop hangs

Greetings, Running /etc/init.d/postgresql stop results in: Stopping postgresql service: [FAILED] I ran an strace on "/usr/local/pgsql/bin/pg_ctl stop -D /data/pgsql/data -s -m fast" and it is sending a SIGINT to processid 5676 Here is a ps of the currently running instance

Re: [ADMIN] postmaster hangs

On Tue, 2005-04-19 at 09:38, Rolf Staege wrote: > hi, > i'm using postgres version 7.4.1 and it run very stable until, may be, > 4 weeks ago. > now the postmaster hangs sometimes for a while (actually since 2 hours) > and doesn't accept connections but comes back anytime. there is no > possibil

Re: [ADMIN] postmaster hangs

Rolf Staege <[EMAIL PROTECTED]> writes: > i'm using postgres version 7.4.1 and it run very stable until, may be, > 4 weeks ago. > now the postmaster hangs sometimes for a while (actually since 2 hours) > and doesn't accept connections but comes back anytime. there is no > possibility to stop th

[ADMIN] postmaster hangs

hi, i'm using postgres version 7.4.1 and it run very stable until, may be, 4 weeks ago. now the postmaster hangs sometimes for a while (actually since 2 hours) and doesn't accept connections but comes back anytime. there is no possibility to stop the postmaster. even a kill -9 (it's only the d

[ADMIN] postmaster eating up memory

Hello, I am running AOLserver with postmaster connecting to my PostgreSQL DB backend, and recently ran into a problem restarting my server, to which I used a kill -9 on my AOLserver processes ($ kill -9 nsd) to release the bound IP. The problem now is that, when I start the server up again, it is

[ADMIN] Postmaster stops after starting--solution

In the October 2004 thread "postmaster stopps" Tom Lane et al. suggested better logging to capture error messages when postmaster silently stops after starting. I was getting silent stops whenever booting the host, so I tried to follow that advice. I found that redirecting the standard and erro

Re: [ADMIN] postmaster stopps

Andrew Sullivan <[EMAIL PROTECTED]> writes: >> LOG: unexpected EOF on client connection > These are cases where the client has gone away without shutting down > its connection properly. At the TCP timeout, the postmaster checks > the client, discovers it isn't there, and shuts down the connectio

Re: [ADMIN] postmaster stopps

On Tue, Oct 19, 2004 at 01:14:10PM +1000, Ashley Maher wrote: > My original post stated I'd had the postmaster stop without explanation. > I now have log files. I can see nothing in messaegs or syslog of interest. I agree there's not much there: > LOG: unexpected EOF on client connection > LOG:

Re: [ADMIN] postmaster stopps

Tom Lane wrote: When you've got some evidence to look at, we'll be glad to help you interpret it, but there's no point in speculating without evidence. Thanks Tom, My original post stated I'd had the postmaster stop without explanation. I now have log files. I can see nothing in messaegs or sys

Re: [ADMIN] postmaster -i option...

"Taber, Mark" <[EMAIL PROTECTED]> writes: > I restarted our dev postgres instance today with the -i option, and now, > using 'ps,', I am not able to see connections to the database any longer. > The production instance (running only with the -D option) shows the > connections. Am I going crazy, mi

[ADMIN] postmaster -i option...

I restarted our dev postgres instance today with the -i option, and now, using 'ps,', I am not able to see connections to the database any longer. The production instance (running only with the -D option) shows the connections. Am I going crazy, missing something obvious? I'm using the command 'p

Re: [ADMIN] postmaster stopps

Ashley Maher <[EMAIL PROTECTED]> writes: > I installed postgresql-7.4.3 about three months ago. > Twice, with no known reason the postmaster has stopped. The postmaster is not known for "just stopping". There will certainly be some evidence either in the postmaster's log (if it aborted for some

[ADMIN] postmaster stopps

G'day, I installed postgresql-7.4.3 about three months ago. Twice, with no known reason the postmaster has stopped. I searched the lists for this but obviousely I'm not searching for the right thing. (couple thousand replies, little relevance) Hints, Ideas appreciated. Regards, Ashley ---

Re: [ADMIN] Postmaster terminated without any error message

roger wrote: > Thanks for your information. I couldn't find the "ulimit" setting in > postgresql.conf. Where can I find it? I use the default settings in pgsql. > Emh. ulimit is a OS command. Do an: ulimit -a and let us know... Regards Gaetano Mendola ---(end of broadca

Re: [ADMIN] Postmaster terminated without any error message

ECTED]> Cc: <[EMAIL PROTECTED]> Sent: Sunday, October 10, 2004 3:29 PM Subject: Re: [ADMIN] Postmaster terminated without any error message > "roger" <[EMAIL PROTECTED]> writes: > > We have Postgresql 7.2 under Redhat 7.2. Postmaster can be started and we c= &

Re: [ADMIN] postmaster terminated abnormally..

[EMAIL PROTECTED] wrote: Hi, Under what circumstances would the postmaster receive signal 11 my postgres server crashed today and analysis of log yeilded sig 11 is SIGSEGV . Any idea on how it prevent it? Are you running your own functions written in C ? Regards Gaetano Mendola -

[ADMIN] postmaster terminated abnormally..

Hi, Under what circumstances would the postmaster receive signal 11 my postgres server crashed today and analysis of log yeilded sig 11 is SIGSEGV . Any idea on how it prevent it? Regds rmallah. LOG: server process (PID 19852) was terminated by signal 11 LOG: terminating any other active

Re: [ADMIN] Postmaster hogs CPU

--- "scott.marlowe" <[EMAIL PROTECTED]> wrote: > On Wed, 5 May 2004, Chris Gamache wrote: > Have you read: > > http://www.varlena.com/varlena/GeneralBits/Tidbits/perf.html > > yet? It may just be that you don't have enough shared_buffers or whatnot. Absolutely. I have a copy on my desk, and o

Re: [ADMIN] Postmaster hogs CPU

On Thu, 6 May 2004, Gaetano Mendola wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Tom Lane wrote: > > | Gaetano Mendola <[EMAIL PROTECTED]> writes: > | > |>You can basically renice the process that is performing the query. > | > | > | However, that's unlikely to do anything very p

Re: [ADMIN] Postmaster hogs CPU

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tom Lane wrote: | Gaetano Mendola <[EMAIL PROTECTED]> writes: | |>You can basically renice the process that is performing the query. | | | However, that's unlikely to do anything very pleasant, since you'll have | priority-inversion problems. "nice" ha

Re: [ADMIN] Postmaster hogs CPU

Gaetano Mendola <[EMAIL PROTECTED]> writes: > You can basically renice the process that is performing the query. However, that's unlikely to do anything very pleasant, since you'll have priority-inversion problems. "nice" has no idea when the process is holding a lock that someone else wants ...

Re: [ADMIN] Postmaster hogs CPU

Chris Gamache wrote: > What can be done to allow for smarter preemption? Could I do anything at the OS > level to throttle that particular postmaster's process? I'm running (IMO) a > balanced config, but there's always room for improvement. Its that oddball > query that comes around once every s

Re: [ADMIN] Postmaster hogs CPU

On Wed, 5 May 2004, Chris Gamache wrote: > When I run an query (that I have identified as expensive, and non-critical), I > would like to be able to take its priority down a few notches to allow the > standard every-day tasks of the DB to run unhindered. As it stands, postmasters > elbow each othe

[ADMIN] Postmaster hogs CPU

When I run an query (that I have identified as expensive, and non-critical), I would like to be able to take its priority down a few notches to allow the standard every-day tasks of the DB to run unhindered. As it stands, postmasters elbow each other out for processor time, and it seems like one ex

[ADMIN] postmaster hangs up - no log entry

Hi All, could anybody suggest me something in connection with the following problem? The posmaster process (7.3.2 on an RH7.1 box) hangs up during some operation. There is no log entry which could indicate the reason of the error. Just stops working. Where should I start it? Thank you in advance.

Re: [ADMIN] postmaster dead but backends still running?

On Thu, 19 Jun 2003, Tom Lane wrote: > Charles Hornberger <[EMAIL PROTECTED]> writes: > > However, I think I know the cause (though I haven't tested to see if this > > indeed causes the postmaster to die): A few hours before I noticed that > > the postmaster was dead, one of the sysadmins made a t

Re: [ADMIN] postmaster dead but backends still running?

Charles Hornberger <[EMAIL PROTECTED]> writes: > However, I think I know the cause (though I haven't tested to see if this > indeed causes the postmaster to die): A few hours before I noticed that > the postmaster was dead, one of the sysadmins made a typo that caused an > NFS mount to become unava

Re: [ADMIN] postmaster dead but backends still running?

On Tue, 17 Jun 2003, Tom Lane wrote: > Charles Hornberger <[EMAIL PROTECTED]> writes: > > Other things I perhaps ought to mention: Trying to stop the postmaster > > using pg_ctl fails (unsurprisingly, since pg_ctl relies on > > /var/pgsql/data/postmaster.pid, which contains a nonexistent PID); I >

Re: [ADMIN] postmaster dead but backends still running?

Charles Hornberger <[EMAIL PROTECTED]> writes: > Other things I perhaps ought to mention: Trying to stop the postmaster > using pg_ctl fails (unsurprisingly, since pg_ctl relies on > /var/pgsql/data/postmaster.pid, which contains a nonexistent PID); I > haven't tried to start a new postmaster ye

Re: [ADMIN] postmaster dead but backends still running?

Other things I perhaps ought to mention: Trying to stop the postmaster using pg_ctl fails (unsurprisingly, since pg_ctl relies on /var/pgsql/data/postmaster.pid, which contains a nonexistent PID); I haven't tried to start a new postmaster yet, because the old backends are hanging around. Nor h

[ADMIN] postmaster dead but backends still running?

I've got what looks like a really strange situation on my hands (or else I've got a normal situation that I'm looking at strangely): It appears that the main postmaster process is dead & gone, but I have a bunch of backends still running. I can't connect to the database server any more, but a b

Re: [ADMIN] postmaster failing to shut down

use command ps to find out who is still connect db, terminate those sessions then try again.     Jie Liang  -Original Message-From: Mona Gamboa [mailto:[EMAIL PROTECTED]]Sent: Wednesday, December 25, 2002 12:13 AMTo: [EMAIL PROTECTED]Subject: [ADMIN] postmaster failing to

Re: [ADMIN] postmaster failing to shut down

"Mona Gamboa" <[EMAIL PROTECTED]> writes: ;; Hi, ;; I'm new to PostgreSQL--have been using it for 3-4 months now. ;; I've been porting our Oracle DB and applications to PostgreSQL ;; and I am using the latest release 7.3. ;; ;; Anyway, when I do try to shutdown the postmaster with th

[ADMIN] postmaster failing to shut down

Hi, I'm new to PostgreSQL--have been using it for 3-4 months now. I've been porting our Oracle DB and applications to PostgreSQL and I am using the latest release 7.3.   Anyway, when I do try to shutdown the postmaster with the following command:   pg_ctl -D /home/postgres/pgsql/DATA stop -m

Re: [ADMIN] postmaster shutdown

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 di

[ADMIN] postmaster shutdown

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

Re: [ADMIN] postmaster shutdown - LWLockAcquire?

"Markus Wollny" <[EMAIL PROTECTED]> writes: > This is the relevant bit of the Logfile: What are your client(s) doing to provoke this crash? (If you don't already know, try running the postmaster at -d2 to get logging of queries. Might want to turn on log_connections and log_pid too.) I doubt t

[ADMIN] postmaster shutdown - LWLockAcquire?

Hello! 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 c

Re: [ADMIN] postmaster problem....

"Nitesh" <[EMAIL PROTECTED]> wrote: > I'm using postgres as an backend with java servlet/jsp using linux as > operating system but when i see the see the CPU process using TOP command > than what i found that postmaster is using 97% of CPU which raise my system > speed very slow. so could u pls he

[ADMIN] postmaster problem....

I'm using postgres as an backend with java servlet/jsp using linux as operating system but when i see the see the CPU process using TOP command than what i found that postmaster is using 97% of CPU which raise my system speed very slow. so could u pls help me to sort out my problem that how can

Re: [ADMIN] postmaster problem

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

Re: [ADMIN] postmaster problem

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 c

[ADMIN] postmaster problem

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

Re: [ADMIN] Postmaster will not start???

On Monday, November 19, 2001, at 03:30 AM, Eric Theis wrote: > I am running PostgreSQL 7.1.2/3 on Mandrake 8.1. My problem (well my > immediate problem) is that the Postmaster will not start. I installed > MDK a > couple months ago. In that time, Postgres has started fine until a > couple

[ADMIN] Postmaster will not start???

I am running PostgreSQL 7.1.2/3 on Mandrake 8.1. My problem (well my immediate problem) is that the Postmaster will not start. I installed MDK a couple months ago. In that time, Postgres has started fine until a couple days ago. I do not get any messages (either on screen or in syslog), but

Re: [ADMIN] postmaster dies with ssl lib error

Hi Randall, It looks like one of the Solaris patches has changed the behaviour of ld, and this is causing it to not find the openssl 0.9.6 libraries when PostgreSQL tries to load. You'll probably have to take some time and read the info in each patch to try and determine which patch caused the c

[ADMIN] postmaster dies with ssl lib error

Suddenly getting this error on start on a Solaris 8 system (after applying a bunch of patches) > /usr/local/pgsql/bin/postmaster -D /export/spare/home/postgres/data & ld.so.1: /usr/local/pgsql/bin/postmaster: fatal: libssl.so.0.9.6: open failed: No such file or directory [1] 1959 [1]Killed

[ADMIN] postmaster pid and ps

Anyone know why my new install of 7.1.3 seems to run fine but the pid does not appear in a ps aux run as root, postgres or any other user thanks, morgan ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster

Re: [ADMIN] Postmaster crash and failed restart. How much space to allocate.

David Stanaway <[EMAIL PROTECTED]> writes: > My postmaster just crashed , it was 7.1release (Debian package version > 4). I'd suggest an update to 7.1.3. Earlier 7.1 releases have problems with the WAL logfiles growing unreasonably large during long transactions. regard

Re: [ADMIN] Postmaster crash and failed restart. How much space toallocate.

David Stanaway writes: > It appears that it was due to running out of space. > Are there any quick tips for receiving notification of critical errors > such as this, and how much breathing space to leave on the filesystem > for the database transaction logs. As you found out for yourself, at lea

[ADMIN] Postmaster crash and failed restart. How much space to allocate.

Hi all, My postmaster just crashed , it was 7.1release (Debian package version 4). I found that the postmaster processes was not running and restarted the postmaster (Unsuccessfully.. ) It appears that it was due to running out of space. Are there any quick tips for receiving notification of

[ADMIN] postmaster successfully started?

after starting the postmaster: pg_ctl -o "-o -F -B 3000 -S -N2 -ps -pn" start postmaster successfully started so the postmaster is started right? but I keep on getting the following createdb test1 psql: connectDBStart() -- connect() failed: No such file or directory Is the postmaster runn

[ADMIN] postmaster unexpected stop

Hi,   I have a problem whit postgreSQL 7.1! The postmaster unxpected stop and report this message in the log file:   DEBUG: StartTransactionCommand TopMemoryContext: 90136 total in 11 blocks; 20072 free (6 chunks); 70064 used TopTransactionContext: 8192 total in 1 blocks; 8176 free (0 chunks); 16

[ADMIN] Postmaster hangs until Ctrl-C

When I run postmaster, the system hangs until I Ctrl-C.   I have a VA Linux box. Postgresql 6.4 was installed at the factory with root ownership and permissions. I read the FAQ and Admin manual re installation. There was no postgres user although VA did create a postgres group. I created a p

  1   2   >