Re: [BUGS] BUG #2786: PGADMIN 1.6
Gilberto Xavier wrote: The following bug has been logged online: Bug reference: 2786 Logged by: Gilberto Xavier Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1 Operating system: Linux and Windows Description:PGADMIN 1.6 Details: Where was set the backup and restore capability into the new version of PGAdmin - 1.6.0. It seens that is not available. Am I correct? That's a bug that slipped in at the last minute :-( It has been fixed for 1.6.1, but in the meantime, if you add the directory containing pg_dump and pg_restore (the pgAdmin installation directory on Windows) to your system path and restart pgAdmin it should solve the problem. Regards, Dave ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [BUGS] BUG #2784: Performance serious degrades over a period of a month
Michael Simms wrote: The following bug has been logged online: Bug reference: 2784 Logged by: Michael Simms Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1.4 Operating system: Linux kernel 2.6.12 Description:Performance serious degrades over a period of a month Details: OK, we have a database that runs perfectly well after a dump and restore, but over a period of a month or two, it just degrades to the point of uselessness. vacuumdb -a is run every 24 hours. We have also run for months at a time using -a -z but the effect doesnt change. You might have a hung transaction that never finishes open, which prevents vacuum from removing old tuple versions. Or you might have too low FSM settings as others suggested. I'd try running VACUUM VERBOSE by hand, and taking a good look at the output. If there's nothing obviously wrong with it, please send the output back to the list (or pgsql-performance, as Tom suggested), and maybe we can help. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[BUGS] BUG #2790: constructor for int2vector seems to be buggy
The following bug has been logged online: Bug reference: 2790 Logged by: Gurjeet Singh Email address: [EMAIL PROTECTED] PostgreSQL version: 8.2beta3 Operating system: Windows Description:constructor for int2vector seems to be buggy Details: I couldn't find any documentation for the data type 'int2vector', so I assume it is unsupported. And moreover, probably I am using an unsupported syntax for populating it, so it may be not that high on priority. But still filing, in case it uncovers something else. In the first INSERT statement, the array elements are separated by a comma and a space; in the second one, the ones that are separated by just a comma, do not get inserted! I could not reproduce it in standard inetegr arrays. Session o/p: postgres=# select version(); version PostgreSQL 8.2beta3 on i686-pc-mingw32, compiled by GCC gcc.exe (GCC) 3.2.3 (mi ngw special 20030504-1) (1 row) postgres=# create table t ( a int2vector ); CREATE TABLE postgres=# insert into t values ( '1, 2, 3' ); INSERT 0 1 postgres=# insert into t values ( '1,2,3, 4' ); INSERT 0 1 postgres=# select * from t; a --- 1 2 3 1 4 (2 rows) postgres=# Best regards, -- [EMAIL PROTECTED] [EMAIL PROTECTED] gmail | hotmail | yahoo }.com ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [BUGS] BUG #2781: database dump/restore problems
regarding pg_dump: where there some changes from b3 to rc1 that would explain the resulting rc1 pg_dump output (-c) being half as big as with b3? No... regards, tom lane well, it was 300mb before rc1, and now its only 188mb. inbetween i did a vacuum full on one table. that shoulnd't affect backup size, should it? i'll restore one of the new backups later on to be sure all data is still there. - thomas ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [BUGS] BUG #2790: constructor for int2vector seems to be buggy
Gurjeet Singh [EMAIL PROTECTED] writes: In the first INSERT statement, the array elements are separated by a comma and a space; in the second one, the ones that are separated by just a comma, do not get inserted! The syntax is space-separated integers; where did you get the idea to use commas? regards, tom lane ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
Re: [BUGS] BUG #2790: constructor for int2vector seems to be buggy
On 11/28/06, Tom Lane [EMAIL PROTECTED] wrote: The syntax is space-separated integers; where did you get the idea to use commas? I donno... I just tried and it worked. But silently ignoring invalid input...!!??? Potential bug's symptoms: quote from=http://www.postgresql.org/docs/current/static/bug-reporting.html A program accepts invalid input without a notice or error message. But keep in mind that your idea of invalid input might be our idea of an extension or compatibility with traditional practice. /quote Or is it a 'extension or compatibility with traditional practice'? BTW, is int2vector really documented? I also found that abstime() works, but couldn't find any documentation for it! (except for \df abstime) Regards, -- [EMAIL PROTECTED] [EMAIL PROTECTED] gmail | hotmail | yahoo }.com
Re: [BUGS] BUG #2785: Exception Issue
Tom, Thank you for your input. I found a way to check for it by counting the return from a count. Thanks again for your help. PAT From: Tom Lane [EMAIL PROTECTED] To: Patrick Hayes [EMAIL PROTECTED] CC: pgsql-bugs@postgresql.org Subject: Re: [BUGS] BUG #2785: Exception Issue Date: Mon, 27 Nov 2006 22:05:04 -0500 Patrick Hayes [EMAIL PROTECTED] writes: I get the following error. postgres-# language plpgsql; ERROR: unrecognized exception condition no_data CONTEXT: compile of PL/pgSQL function chip_pps_data_check near line 101 Indeed, because no_data is not an error condition, so EXCEPTION can't catch it. Possibly you could do something with testing the FOUND variable instead. regards, tom lane _ MSN Shopping has everything on your holiday list. Get expert picks by style, age, and price. Try it! http://shopping.msn.com/content/shp/?ctId=8000,ptnrid=176,ptnrdata=200601tcode=wlmtagline ---(end of broadcast)--- TIP 6: explain analyze is your friend
[BUGS] BUG #2792: not able to install postgress
The following bug has been logged online: Bug reference: 2792 Logged by: Santhinesh Kumar Email address: [EMAIL PROTECTED] PostgreSQL version: 7.1.3 Operating system: Fedora - 4 Description:not able to install postgress Details: I tried to install postgress of version 7.1.4. But I faced some problems while installing. When I typed ./configure command there was a error at the last. It was that could not configure the parameters given in the ./configure command. ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[BUGS] BUG #2791: Error while commiting
The following bug has been logged online: Bug reference: 2791 Logged by: Raman Dabhade Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1 Operating system: Win XP Description:Error while commiting Details: ERROR: SPI_execute_plan failed executing query commit: SPI_ERROR_TRANSACTION CONTEXT: PL/pgSQL function processrecords line 4 at SQL statement When executing following procedure: CREATE OR REPLACE FUNCTION processRecords() RETURNS int8 AS $BODY$ declare begin commit ; return 0; end; $BODY$ LANGUAGE 'plpgsql' VOLATILE; ---(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] BUG #2792: not able to install postgress
Santhinesh Kumar wrote: The following bug has been logged online: Bug reference: 2792 Logged by: Santhinesh Kumar Email address: [EMAIL PROTECTED] PostgreSQL version: 7.1.3 Operating system: Fedora - 4 Description:not able to install postgress Details: I tried to install postgress of version 7.1.4. But I faced some problems while installing. When I typed ./configure command there was a error at the last. It was that could not configure the parameters given in the ./configure command. So don't install that version -- choose a newer one, for example 8.1.5. Even better, install the one provided with your operating system. -- Alvaro Herrerahttp://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support ---(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
[BUGS] could not rename temporary statistics file: No such file or directory
I'm continuing to have file-access related errors with 8.1.5 on Windows. (see my previous post here http://tinyurl.com/yfqhnm) Today I'm having a new problem, which results in the following log output: 2006-11-28 12:15:45 LOG: could not rename temporary statistics file global/pgstat.tmp to global/pgstat.stat: No such file or directory 2006-11-28 12:15:48 LOG: could not rename temporary statistics file global/pgstat.tmp to global/pgstat.stat: No such file or directory 2006-11-28 12:15:49 LOG: could not rename temporary statistics file global/pgstat.tmp to global/pgstat.stat: No such file or directory There are no noticeable effects from these errors that I know of. I've looked at file permissions, etc. and everything seems fine. I've got FileMon running and don't see anything that is obviously related to pgstat... Any ideas what could cause this problem? Jeremy Haile ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [BUGS] fsync and semctl errors with 8.1.5/win32
OK - after uninstalling the virus scanner (McAfee), I still get the same disk access errors. Here's a few seconds of the log output (this has been going on for 10 mins as of this e-mail being sent): 2006-11-28 16:16:10 LOG: could not fsync segment 0 of relation 1663/16404/30267: Permission denied 2006-11-28 16:16:10 ERROR: storage sync failed on magnetic disk: Permission denied 2006-11-28 16:16:11 LOG: could not fsync segment 0 of relation 1663/16404/30267: Permission denied 2006-11-28 16:16:11 ERROR: storage sync failed on magnetic disk: Permission denied 2006-11-28 16:16:12 LOG: could not fsync segment 0 of relation 1663/16404/30267: Permission denied 2006-11-28 16:16:12 ERROR: storage sync failed on magnetic disk: Permission denied 2006-11-28 16:16:13 LOG: could not fsync segment 0 of relation 1663/16404/30267: Permission denied 2006-11-28 16:16:13 ERROR: storage sync failed on magnetic disk: Permission denied Here's the FileMon output from the same seconds: 4:16:10 PM postgres.exe:3168 OPENC:\Program Files\PostgreSQL\8.1\data\base\16404\30267 DELETE PEND Options: Open Access: 0012019F 4:16:11 PM postgres.exe:3168 OPENC:\Program Files\PostgreSQL\8.1\data\base\16404\30267 DELETE PEND Options: Open Access: 0012019F 4:16:12 PM postgres.exe:3168 OPENC:\Program Files\PostgreSQL\8.1\data\base\16404\30267 DELETE PEND Options: Open Access: 0012019F 4:16:13 PM postgres.exe:3168 OPENC:\Program Files\PostgreSQL\8.1\data\base\16404\30267 DELETE PEND Options: Open Access: 0012019F This is an incredibly bad problem for me. I'd really appreciate any help! Jeremy On Mon, 27 Nov 2006 12:14:00 -0500, Jeremy Haile [EMAIL PROTECTED] said: Thanks for the feedback. If you don't mind, what version of PostgreSQL are you running? I'm trying to bring PostgreSQL into this company - they are primarily a Windows/SQL Server shop (although Java software development) I've already gotten comments similar to Why don't you just switch to SQL Server? - so I'm hoping to find a workaround before I get forced to switch DB platforms. As it is, my application seems unreliable because I haven't been able to resolve the PostgreSQL hanging problems in Windows. If I had my way, I'd switch the server to Linux - but alas, that hasn't been an option so far. I know this may be the wrong list to ask this question on - but as I'm an outspoken PostgreSQL advocate, I'd like your opinions. If I am unable to resolve these PostgreSQL issues given my constraints, will I likely have less problems running MySQL/InnoDB on Windows? (since it has had a native Windows build for much longer) On Mon, 27 Nov 2006 16:40:57 +, Dave Page [EMAIL PROTECTED] said: Jeremy Haile wrote: I've gotten pushback from my organization on removing antivirus from the servers completely. Are there any antiviruses that are known to be compatible with PostgreSQL/win32? All my boxes (2 build farm members, 1 production server, and the laptop on which the official releases are built and tested) run Sophos Anti Virus (http://www.sophos.com/products/es/endpoint/sav.html), with no problems. Regards, Dave ---(end of broadcast)--- TIP 6: explain analyze is your friend ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings ---(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] fsync and semctl errors with 8.1.5/win32
I forgot to mention - this problem is occurring on multiple Windows machines. One of them is running Windows XP Professional. The other is running Windows Server 2003. I have disabled indexing, virus scanning, and all non-essential services on both of them. The problem continues to show up even when no queries are being run (although it might always start while queries are running) On Tue, 28 Nov 2006 16:18:56 -0500, Jeremy Haile [EMAIL PROTECTED] said: OK - after uninstalling the virus scanner (McAfee), I still get the same disk access errors. Here's a few seconds of the log output (this has been going on for 10 mins as of this e-mail being sent): 2006-11-28 16:16:10 LOG: could not fsync segment 0 of relation 1663/16404/30267: Permission denied 2006-11-28 16:16:10 ERROR: storage sync failed on magnetic disk: Permission denied 2006-11-28 16:16:11 LOG: could not fsync segment 0 of relation 1663/16404/30267: Permission denied 2006-11-28 16:16:11 ERROR: storage sync failed on magnetic disk: Permission denied 2006-11-28 16:16:12 LOG: could not fsync segment 0 of relation 1663/16404/30267: Permission denied 2006-11-28 16:16:12 ERROR: storage sync failed on magnetic disk: Permission denied 2006-11-28 16:16:13 LOG: could not fsync segment 0 of relation 1663/16404/30267: Permission denied 2006-11-28 16:16:13 ERROR: storage sync failed on magnetic disk: Permission denied Here's the FileMon output from the same seconds: 4:16:10 PM postgres.exe:3168 OPENC:\Program Files\PostgreSQL\8.1\data\base\16404\30267 DELETE PEND Options: Open Access: 0012019F 4:16:11 PM postgres.exe:3168 OPENC:\Program Files\PostgreSQL\8.1\data\base\16404\30267 DELETE PEND Options: Open Access: 0012019F 4:16:12 PM postgres.exe:3168 OPENC:\Program Files\PostgreSQL\8.1\data\base\16404\30267 DELETE PEND Options: Open Access: 0012019F 4:16:13 PM postgres.exe:3168 OPENC:\Program Files\PostgreSQL\8.1\data\base\16404\30267 DELETE PEND Options: Open Access: 0012019F This is an incredibly bad problem for me. I'd really appreciate any help! Jeremy On Mon, 27 Nov 2006 12:14:00 -0500, Jeremy Haile [EMAIL PROTECTED] said: Thanks for the feedback. If you don't mind, what version of PostgreSQL are you running? I'm trying to bring PostgreSQL into this company - they are primarily a Windows/SQL Server shop (although Java software development) I've already gotten comments similar to Why don't you just switch to SQL Server? - so I'm hoping to find a workaround before I get forced to switch DB platforms. As it is, my application seems unreliable because I haven't been able to resolve the PostgreSQL hanging problems in Windows. If I had my way, I'd switch the server to Linux - but alas, that hasn't been an option so far. I know this may be the wrong list to ask this question on - but as I'm an outspoken PostgreSQL advocate, I'd like your opinions. If I am unable to resolve these PostgreSQL issues given my constraints, will I likely have less problems running MySQL/InnoDB on Windows? (since it has had a native Windows build for much longer) On Mon, 27 Nov 2006 16:40:57 +, Dave Page [EMAIL PROTECTED] said: Jeremy Haile wrote: I've gotten pushback from my organization on removing antivirus from the servers completely. Are there any antiviruses that are known to be compatible with PostgreSQL/win32? All my boxes (2 build farm members, 1 production server, and the laptop on which the official releases are built and tested) run Sophos Anti Virus (http://www.sophos.com/products/es/endpoint/sav.html), with no problems. Regards, Dave ---(end of broadcast)--- TIP 6: explain analyze is your friend ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [BUGS] fsync and semctl errors with 8.1.5/win32
I forgot to mention - this problem is occurring on multiple Windows machines. One of them is running Windows XP Professional. The other is running Windows Server 2003. I have disabled indexing, virus scanning, and all non-essential services on both of them. The problem continues to show up even when no queries are being run (although it might always start while queries are running) seems exactly what i'm noticing since 8.2x on windows 2003 as well - no disk services (backup, virus, ...) are running that would block files, and processmon/filemon always show that the files in question are locked by pgsql processes... under higher insert/update load, the errors appear more often here, do you experience the same finding when loading bulk data? - thomas ---(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] fsync and semctl errors with 8.1.5/win32
Jeremy Haile [EMAIL PROTECTED] writes: Here's a few seconds of the log output (this has been going on for 10 mins as of this e-mail being sent): 2006-11-28 16:16:10 LOG: could not fsync segment 0 of relation 1663/16404/30267: Permission denied 2006-11-28 16:16:10 ERROR: storage sync failed on magnetic disk: Permission denied Here's the FileMon output from the same seconds: 4:16:10 PM postgres.exe:3168 OPENC:\Program Files\PostgreSQL\8.1\data\base\16404\30267 DELETE PEND Options: Open Access: 0012019F I still don't want to make mdsync() treat EACCES as an ignorable error. However, in this situation we've got an infinite loop because the checkpoint will never succeed and thus the bgwriter will never reach smgrcloseall(), which seems to be what's needed to allow the deleted file to die the real death. Perhaps a suitable workaround would be to make the bgwriter do smgrcloseall in its error recovery path? That is /* * Sleep at least 1 second after any error. A write error is likely * to be repeated, and we don't want to be filling the error logs as * fast as we can. */ pg_usleep(100L); + + /* Drop open files to allow deleted files to really go away */ + smgrcloseall(); } /* We can now handle ereport(ERROR) */ PG_exception_stack = local_sigjmp_buf; Perhaps this should be #ifdef WIN32, although there's probably no harm in doing it on Unixen too. Can someone test this idea? 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] fsync and semctl errors with 8.1.5/win32
Yes - processmon always shows the files being locked by postgres.exe processes. My database is being used as a data warehouse, so about all I am doing is bulk insert/updates. I have a job that runs every 5 minutes and loads data into the database. I typically load between 10,000 and 100,000 rows every 5 minutes into my fact tables, although I also make use of transition tables, dimension tables, etc. that get inserts/updates as well. I see the problem occur 3-4 times a day on average, but I don't know how to reproduce it other than letting it run for a while. On Tue, 28 Nov 2006 22:31:42 +0100, Thomas H. [EMAIL PROTECTED] said: I forgot to mention - this problem is occurring on multiple Windows machines. One of them is running Windows XP Professional. The other is running Windows Server 2003. I have disabled indexing, virus scanning, and all non-essential services on both of them. The problem continues to show up even when no queries are being run (although it might always start while queries are running) seems exactly what i'm noticing since 8.2x on windows 2003 as well - no disk services (backup, virus, ...) are running that would block files, and processmon/filemon always show that the files in question are locked by pgsql processes... under higher insert/update load, the errors appear more often here, do you experience the same finding when loading bulk data? - thomas ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [BUGS] fsync and semctl errors with 8.1.5/win32
Perhaps this should be #ifdef WIN32, although there's probably no harm in doing it on Unixen too. Can someone test this idea? if magnus/dave could provide me a patched rc1 exe, i could run it in our semi-productive environment for some tests. - thomas ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [BUGS] fsync and semctl errors with 8.1.5/win32
I am currently running 8.1.5, but I'm willing to upgrade to whatever version, use a patched exe, etc. Just let me know what I need to do. On Tue, 28 Nov 2006 23:39:00 +0100, Thomas H. [EMAIL PROTECTED] said: Perhaps this should be #ifdef WIN32, although there's probably no harm in doing it on Unixen too. Can someone test this idea? if magnus/dave could provide me a patched rc1 exe, i could run it in our semi-productive environment for some tests. - thomas ---(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
