Re: [BUGS] BUG #2468: how to create auto-generate primary key
Please don't use the bug reporting facilities to ask support questions. pgsql-general@postgresql.org would be a reasonable list to ask your question. ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [BUGS] BUG #2469: Error in connection to the server
Please don't use the bug reporting facilities to ask support questions. Your question would be appropiate for either the pgsql-general@postgresql.org or [EMAIL PROTECTED] mailing lists. ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [BUGS] BUG #2465: Installation
On Fri, Jun 02, 2006 at 07:47:02PM +, Patrick Hayes wrote: > > The following bug has been logged online: > > Bug reference: 2465 > Logged by: Patrick Hayes > Email address: [EMAIL PROTECTED] > PostgreSQL version: 8.1 > Operating system: Window XP > Description:Installation > Details: > > I have installed version 8.1. I am trying to access the console. This will > not allow me access. I know I am entering the correct password. I'd bet that you're not. :) I suggest going into pg_hba.conf and enabling trust access. Then connect and change the password and change pg_hba.conf back. You'll need to reload the config after each pg_hba.conf change. -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.comwork: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [BUGS] stopping server does not remove external_pid_file
Martin Pitt wrote: > I just played around with external_pid_file in 8.1.4. I noticed that > the file is created and filled properly, but it is not removed again > when the server is stopped. > Looking at the code I see this comment in src/backend/postmaster/postmaster.c /* Should we remove the pid file on postmaster exit? */ IMHO, yes. It's not useful anymore. Maybe some simple test in pmdie(). I'm too tired to code something now. :( -- Euler Taveira de Oliveira http://www.timbira.com/ ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [BUGS] stopping server does not remove external_pid_file
Euler Taveira de Oliveira <[EMAIL PROTECTED]> writes: > Martin Pitt wrote: >> I just played around with external_pid_file in 8.1.4. I noticed that >> the file is created and filled properly, but it is not removed again >> when the server is stopped. >> > Looking at the code I see this comment in > src/backend/postmaster/postmaster.c > /* Should we remove the pid file on postmaster exit? */ > IMHO, yes. It's not useful anymore. [ shrug... ] If the postmaster crashes, it would certainly fail to remove the pidfile. So I'd argue that your unnamed external script that is expecting the pidfile to go away needs work: if it's not verifying the PID given in the file, it's broken. regards, tom lane ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [BUGS] stopping server does not remove external_pid_file
Tom Lane wrote: > Euler Taveira de Oliveira <[EMAIL PROTECTED]> writes: > > Martin Pitt wrote: > >> I just played around with external_pid_file in 8.1.4. I noticed that > >> the file is created and filled properly, but it is not removed again > >> when the server is stopped. > >> > > Looking at the code I see this comment in > > src/backend/postmaster/postmaster.c > > > /* Should we remove the pid file on postmaster exit? */ > > > IMHO, yes. It's not useful anymore. > > [ shrug... ] If the postmaster crashes, it would certainly fail to > remove the pidfile. So I'd argue that your unnamed external script > that is expecting the pidfile to go away needs work: if it's not > verifying the PID given in the file, it's broken. Doesn't removing the file reduce the chances of failing to start later in case another postmaster already has that pid? Why do we keep it around? -- Bruce Momjian http://candle.pha.pa.us EnterpriseDBhttp://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [BUGS] stopping server does not remove external_pid_file
Bruce Momjian writes: > Doesn't removing the file reduce the chances of failing to start later > in case another postmaster already has that pid? No, because the external pidfile has zero to do with Postgres' internal behavior. Personally I always thought that the external pidfile was a "feature" we should have rejected. It can never be a particularly reliable guide to what PG is doing, the more especially so if the program looking at it isn't doing any cross-checking, as the OP seems not to be doing. regards, tom lane ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [BUGS] stopping server does not remove external_pid_file
Tom Lane wrote: > Bruce Momjian writes: > > Doesn't removing the file reduce the chances of failing to start later > > in case another postmaster already has that pid? > > No, because the external pidfile has zero to do with Postgres' internal > behavior. > > Personally I always thought that the external pidfile was a "feature" > we should have rejected. It can never be a particularly reliable guide > to what PG is doing, the more especially so if the program looking at it > isn't doing any cross-checking, as the OP seems not to be doing. Oh, it is the "external" file, not the one we automatically create in the /data directory. -- Bruce Momjian http://candle.pha.pa.us EnterpriseDBhttp://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
