I've upgraded to 8.2rc1. I still receive fsync errors all the time, but
I haven't had it freeze yet. With 8.1.5 I was able to reproduce the
freeze very quickly, so this is a good sign! Only time will tell if
it's truly resolved - but I'll post updates to this list either way.
I'm still open to
I doubt this is really "a bug." This usually just means that the server
failed to start for some reason (port already in use, bad configuration,
etc.) Any startup problem with the database will result in this
behavior.
However - what might could be addressed is that it is pretty difficult
to deb
The following bug has been logged online:
Bug reference: 2794
Logged by:
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: macosx
Description:corrupted table pk index
Details:
when i try to reconstruct a table index
reindex table "public
The following bug has been logged online:
Bug reference: 2795
Logged by: Ilia
Email address: [EMAIL PROTECTED]
PostgreSQL version: postgreSQL 8.1
Operating system: windows server 2003 standart edition
Description:can't start service postgre
Details:
I successfully s
The following bug has been logged online:
Bug reference: 2793
Logged by: Thiago dos Santos Alves
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2rc1
Operating system: Windows
Description:Cannot Install (Problem with permitions)
Details:
When I install Postgr
In our case the hanging transactions was killing our in house merge
process that merges the data from our stores to the warehouse.
When we rolled back sp1 no hanging transactions. When we applied sp1
the hanging started again. We took sp1 off and on a couple times and it
happened every time.
-
Jeremy,
My company runs a 200 gig data warehouse. We are running 8.1.2. We were
seeing hanging transactions and occasional semctl errors.
We were also running it on Windows Server 2003. We ended up rolling
back service pack 1 and it seems to have taken care of the hanging
transactions and we
We were also running it on Windows Server 2003. We ended up rolling
back service pack 1 and it seems to have taken care of the hanging
transactions and we haven't seen a semctl error in awhile.
interesting. we're using sp1 & pgsql since day 1 and the problem only
started when testing 8.2b1. bu
Did you run into problems where transactions would hang? If so, did
those disappear in 8.2?
well, i wasn't really able to exactly determine under what conditions that
xlog bug appeared in our case. tho it always was when lots of data is
imported at once within one transaction. under normal lo
Really? That's great news. Maybe I should start testing with 8.2
today.
Did you run into problems where transactions would hang? If so, did
those disappear in 8.2?
On Thu, 30 Nov 2006 15:14:46 +0100, "Thomas H." <[EMAIL PROTECTED]> said:
> > 2006-11-29 23:57:52 LOG: could not rename file
>
2006-11-29 23:57:52 LOG: could not rename file
"pg_xlog/00010019005E" to
"pg_xlog/00010019007F", continuing to try
i had this one as well. good news is: this bug is fixed in 8.2
- thomas
---(end of broadcast)---
TIP 5: d
Last night I received another filesystem-related problem. Shortly after
this problem occurred, I had a connection hang indefinitely, causing my
software to go down all night.
The log output that occurred shortly before the problem is below. After
that, there was no log output by PostgreSQL unt
12 matches
Mail list logo
