Re: [BUGS] BUG #1806: Postmaster takes uses 99% of CPU
Mike Krüger wrote: Sorry, I lost the Email Adress of the List. No problem, just remember to hit "reply all" rather than "reply". There are no problems with other Processes. The System is only slow, when the postmaster Prozess gets the 100 % CPU time. Can I configure it, that this Prozess dont get more than 60 % ? Not really (on Linux anyway). However, if other processes have useful work to do and need CPU time, they will get their fair share. So - if PG is running at 99% CPU (for long periods) that implies all other processes are either waiting for PG to respond anyway, or are waiting for disk/network etc. The system shouldn't feel "slow" or "unresponsive" just because one process is busy. If it does, that might imply swap is being used, or network or disk activity is at a maximum. General system admin is too large a subject to deal with here, but the tools to check documentation for are: top/free/vmstat/iostat/netstat Oh - and make sure your configuration settings are reasonable. Read these two performance-tuning guides: http://www.varlena.com/varlena/GeneralBits/Tidbits/index.php http://www.powerpostgresql.com/PerfList HTH -- Richard Huxton Archonet Ltd ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [BUGS] Cache lookup failed !!!
"Sivaraman K.G" <[EMAIL PROTECTED]> writes: > \d command used to give the existing relations in the database. > But now it is saying : > ERROR : Cache lookup failed for relation 17233. Not a lot of information to go on here. What do you get from select * from pg_class where oid = 17233; Can you do other operations besides \d? regards, tom lane ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [BUGS] BUG #1811: unique index problem
"George Jansen" <[EMAIL PROTECTED]> writes: > [ inconsistent comparison behavior ] > Both old and new databases use SQL_ASCII. Is this a bug? I think it's probably a locale problem; did you initdb the database in C locale? (Check SHOW LC_COLLATE and SHOW LC_CTYPE to be sure.) Usually we see this sort of thing when the locale is expecting characters in a different encoding than what's actually being stored. regards, tom lane ---(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 #1809: invalid pointer on pg_ctl reload
"Chris Hoover" <[EMAIL PROTECTED]> writes: > I was working with my pg_hba.conf file and did a pg_ctl -D reload. I > received the following message, and postgresql shutdown. > [EMAIL PROTECTED] eedi]$ pg_ctl -D /database/data/eedi/ reload > postmaster signaled > [EMAIL PROTECTED] eedi]$ *** glibc detected *** free(): invalid pointer: > 0x082ced00 *** What non-comment entries do you have in postgresql.conf? It's also possible that the problem is being triggered by an unusual entry in one of the other config files, such as pg_hba.conf. Please see if you can narrow down what's causing this. regards, tom lane ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [BUGS] BUG #1812: installation
> Bug reference: 1812 > Logged by: Donald Bahari > Email address: [EMAIL PROTECTED] > PostgreSQL version: 8.0.3 > Operating system: Windows XP Home SP2 > Description:installation > Details: > > in the first screen of the installation the user was set to > postgres and asked for a password, which i gave. there was an > error message and i changed the user and password to > something i had set up in "user accounts" in "control panel". > in control panel i couldn't set up a user "postgres", but i > could set up a different user(e.g. donbah) with a password > and then change the name the name to "postgres", but the > installation gave an error message, so i had to change the > user to "donbah" and use the password i set in control panel. > then i could complete the installation. since i am a beginner > and trying to learn by following from a book, i don't know if > its ok to proceed. i also had difficulty with the > "createuser" command. Not much we can say without seeing the actual error message you received... Out of interest, which book discusses the postgresql installer for win32? I wasn't aware there was one out yet :-) //Magnus ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [BUGS] BUG #1799: Auto Creation of Strong Password fails
> Bug reference: 1799 > Logged by: HAUSERMANN Laurent > Email address: [EMAIL PROTECTED] > PostgreSQL version: 8.0.3 > Operating system: Windows 2000 > Description:Auto Creation of Strong Password fails > Details: > > I ran the Postgresql 8.0.3 msi installer on a "postgres > blank" plateform. > > The Win32 installer asker for creating a user for me, said my > password was weak and replace it... > This feature is really great, but the installer are not able > to connect as this user after this password generation... > > Answering "no" and keeping my "weak" password, permits to > have a valid installation That's interesting - it has always worked for me. What password did it generate that wouldn't work? And what exactly was the error message? //Magnus ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [BUGS] BUG #1805: FATAL: invalid command-line arguments for server process HINT: Try "postgres --help" for more inform
> The following bug has been logged online: > > Bug reference: 1805 > Logged by: Vahe > Email address: [EMAIL PROTECTED] > PostgreSQL version: 8 > Operating system: windows XP > Description:FATAL: invalid command-line arguments for > server process > HINT: Try "postgres --help" for more inform > Details: > > i have installed the provider of the postgreSql and my > connection is opening ,but what i want is the oledb provider > for the postgreSql,i have also dowloaded the pgoledb which > the oledb provider of the postgre in .nET and i have > registered it i have it in the drivers.,but when i try to > connect or to open a connection the following error is occuring. > > FATAL: invalid command-line arguments for server process > HINT: Try "postgres --help" for more information. > > this error is giving me when i try to open the connection Can > you help me solve the problem. > Thank you What connectionstring are you using? This looks like an issue with pgoledb, it's probably better asked on their lists. //Magnus ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [BUGS] BUG #1809: invalid pointer on pg_ctl reload
"CHRIS HOOVER" <[EMAIL PROTECTED]> writes: >> I was working with my pg_hba.conf file and did a pg_ctl -D reload. I >> received the following message, and postgresql shutdown. >> [EMAIL PROTECTED] eedi]$ pg_ctl -D /database/data/eedi/ reload >> postmaster signaled >> [EMAIL PROTECTED] eedi]$ *** glibc detected *** free(): invalid pointer: >> 0x082ced00 *** > I was playing around and had most entries uncommented, even if I did not > change the values. I am attaching the cleaned up postgresql.conf and my > pg_hba.conf files for you. Got it --- we had broken the handling of an explicit specification timezone = unknown in the config file. Thanks for sending along the test case. regards, tom lane ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[BUGS] BUG #1814: Cancelling a CLUSTER changes the OID counter
The following bug has been logged online: Bug reference: 1814 Logged by: Ian Burrell Email address: [EMAIL PROTECTED] PostgreSQL version: 7.4.6 Operating system: RHEL 3 x86_64 Description:Cancelling a CLUSTER changes the OID counter Details: Cancelling a CLUSTER is causing the OID counter to jump forwards. In the test below, it goes from 108 million to 4286 million (close to 2^32). We recently wrapped the OID counter. vodlive=# insert into foo values (1) ; INSERT 108817614 1 Time: 0.675 ms vodlive=# select oid, * from foo ; oid| bar ---+- 108817614 | 1 vodlive=# CLUSTER idx_daily_by_cs_ti_wk_wk_cs_ti ON daily_xtns_by_cable_sys_title_wk ; Cancel request sent ERROR: canceling query due to user request vodlive=# abort ; ROLLBACK vodlive=# insert into foo values (1) ; INSERT 4286822632 1 Time: 0.475 ms vodlive=# select oid, * from foo ; oid | bar +- 4286822632 | 1 (1 row) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [BUGS] BUG #1809: invalid pointer on pg_ctl reload
I was playing around and had most entries uncommented, even if I did not change the values. I am attaching the cleaned up postgresql.conf and my pg_hba.conf files for you. Chris Hoover Application Development System Analyst 2 Companion Technologies 8901 Farrow Rd. Columbia, SC 29203 Phone: (803) 264-3896 E-Mail: [EMAIL PROTECTED] Web: http://www.companiontechnologies.com --( Forwarded letter 1 follows )- Date: Mon, 08 Aug 2005 12:20:56 -0400 To: chris.hoover Cc: [EMAIL PROTECTED] From: [EMAIL PROTECTED] Subject: Re: [BUGS] BUG #1809: invalid pointer on pg_ctl reload "Chris Hoover" <[EMAIL PROTECTED]> writes: > I was working with my pg_hba.conf file and did a pg_ctl -D reload. I > received the following message, and postgresql shutdown. > [EMAIL PROTECTED] eedi]$ pg_ctl -D /database/data/eedi/ reload > postmaster signaled > [EMAIL PROTECTED] eedi]$ *** glibc detected *** free(): invalid pointer: > 0x082ced00 *** What non-comment entries do you have in postgresql.conf? It's also possible that the problem is being triggered by an unusual entry in one of the other config files, such as pg_hba.conf. Please see if you can narrow down what's causing this. regards, tom lane postgresql.conf.mail Description: Binary data pg_hba.conf Description: Binary data ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [BUGS] BUG #1814: Cancelling a CLUSTER changes the OID counter
"Ian Burrell" <[EMAIL PROTECTED]> writes: > Cancelling a CLUSTER is causing the OID counter to jump forwards. In the > test below, it goes from 108 million to 4286 million (close to 2^32). [ scratches head... ] Cannot duplicate this here. Does anyone else see it? regards, tom lane ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [BUGS] BUG #1814: Cancelling a CLUSTER changes the OID counter
"Ian Burrell" <[EMAIL PROTECTED]> writes: > Cancelling a CLUSTER is causing the OID counter to jump forwards. In the > test below, it goes from 108 million to 4286 million (close to 2^32). > We recently wrapped the OID counter. Uh, does the same thing happen if you *don't* cancel it? It looks to me like this could possibly happen due to CheckMaxObjectId() being applied to each OID found in the existing table. CheckMaxObjectId was always a kluge, and I'm not sure that it still has any redeeming social value at all. Can anyone think of a good reason to keep it? regards, tom lane ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
