[BUGS] BUG #5849: Stats Collector Frozen - Autovacuum Not Working Anymore

2011-01-26 Thread Radu Ilie
The following bug has been logged online: Bug reference: 5849 Logged by: Radu Ilie Email address: ri...@wsi.com PostgreSQL version: 8.4.4 32 bit Operating system: Windows 7 Professional 64 bit Description:Stats Collector Frozen - Autovacuum Not Working Anymore Details

Re: [BUGS] BUG #5849: Stats Collector Frozen - Autovacuum Not Working Anymore

2011-01-26 Thread Tom Lane
"Radu Ilie" writes: > PostgreSQL version: 8.4.4 32 bit > We started noticing very poor performance one day ago. Turns out the > autovacuum was no longer working. Perhaps you ran into the cost_limit problem that was fixed in 8.4.6? http://archives.postgresql.org/pgsql-committers/2010-11/msg00186

[BUGS] NO DATA error message in Frontend when querying large datasets

2011-01-26 Thread Jens Kapp
hello, we have postgres 9.0.1 installed on a windows 2008 r2 server. odbc is psqlodbc_09_00_0200.zip. the database has currently a size of around 800mb. it works as expected on the server (pgadmin), but if we try queries for large datasets we get the error message: "No data" from our frontend

[BUGS] BUG #5850: UPDATE statement fails when using aliases

2011-01-26 Thread Joshua Farray
The following bug has been logged online: Bug reference: 5850 Logged by: Joshua Farray Email address: far...@gmail.com PostgreSQL version: 9.0.2 Operating system: Win7 x64 Description:UPDATE statement fails when using aliases Details: Make a table: > CREATE TABLE fo

Re: [BUGS] BUG #5850: UPDATE statement fails when using aliases

2011-01-26 Thread hubert depesz lubaczewski
On Wed, Jan 26, 2011 at 06:05:40PM +, Joshua Farray wrote: > > The following bug has been logged online: > > Bug reference: 5850 > Logged by: Joshua Farray > Email address: far...@gmail.com > PostgreSQL version: 9.0.2 > Operating system: Win7 x64 > Description:UPD

Re: [BUGS] Multicolun index creation never completes on 9.0.1/solaris

2011-01-26 Thread Josh Berkus
> Your logic has nothing to do with what is actually happening. Could we > have a little bit more patience to see what happens next? So, after 15 hours: LOG: finished writing run 20 to tape 19: CPU 588.86s/4484.35u sec elapsed 5160.97 sec STATEMENT: create index "write_log_accounttime_idx" on

Re: [BUGS] Multicolun index creation never completes on 9.0.1/solaris

2011-01-26 Thread Tom Lane
Josh Berkus writes: > ... I'll point out that the elapsed times which trace_sort is giving me > are clearly not clock times; I started this index run at 7pm PST > yesterday and it's been 15 hours, not 2 as the elapsed time would suggest. [ raised eyebrow... ] Those numbers are the differences be

Re: [BUGS] NO DATA error message in Frontend when querying large datasets

2011-01-26 Thread Tom Lane
Jens Kapp writes: > we have postgres 9.0.1 installed on a windows 2008 r2 server. > odbc is psqlodbc_09_00_0200.zip. > the database has currently a size of around 800mb. > it works as expected on the server (pgadmin), but if we try queries for > large datasets we get the error message: "No data"

Re: [BUGS] Multicolun index creation never completes on 9.0.1/solaris

2011-01-26 Thread Josh Berkus
Tom, > [ raised eyebrow... ] Those numbers are the differences between two > gettimeofday() readings. It's really really hard to believe that that's > wrong, unless there's something seriously wrong with your machine. Actually, you're right ... I don't know what time the run27 message was poste

Re: [BUGS] Multicolun index creation never completes on 9.0.1/solaris

2011-01-26 Thread Tom Lane
Josh Berkus writes: > Oh! Actually, it only *did* 27 runs. So it actually completed building > the index. I'd expected trace_sort to give me some kind of completion > message; apologies for not checking all screen windows. Huh, there should be an "external sort ended" message, as well as some

Re: [BUGS] NO DATA error message in Frontend when querying large datasets

2011-01-26 Thread Jens Kapp
hi tom, thanks a lot for your response. the frontend we are trying to use is a well known and spread laboratory system. our consultant has experience with other databases (oracle, sql) that are a lot bigger - with no problems. however i'm wondering that postgres is not working with the lab sy

Re: [BUGS] NO DATA error message in Frontend when querying large datasets

2011-01-26 Thread Korry Douglas
> thanks a lot for your response. > the frontend we are trying to use is a well known and spread laboratory > system. our consultant has experience with other databases (oracle, sql) that > are a lot bigger - with no problems. however i'm wondering that postgres is > not working with the lab sys

Re: [BUGS] Multicolun index creation never completes on 9.0.1/solaris

2011-01-26 Thread Josh Berkus
On 1/26/11 12:13 PM, Tom Lane wrote: > Josh Berkus writes: >> Oh! Actually, it only *did* 27 runs. So it actually completed building >> the index. I'd expected trace_sort to give me some kind of completion >> message; apologies for not checking all screen windows. > > Huh, there should be an "

[BUGS] BUG #5851: ROHS (read only hot standby) needs to be restarted manually in somecases.

2011-01-26 Thread Mark
The following bug has been logged online: Bug reference: 5851 Logged by: Mark Email address: dvlh...@gmail.com PostgreSQL version: 9.0.2 x86_64 Operating system: CentOS release 5.5 (Final) | 2.6.18-194.17.1.el5 #1 SMP X86_64 Description:ROHS (read only hot standby) n

Re: [BUGS] BUG #5800: "corrupted" error messages (encoding problem ?)

2011-01-26 Thread Dave Page
2011/1/27 Génération Amiga : > Hello Dave, > > Any news about that encoding problem ? We've been working with a couple of our friends in Japan, and it looks like one of them has tracked down an issue in the gettext library. It looks like we can work around it. We'l try to get it into the next rele