>Does that mean 8.1.3 works fine on other PCs you have, but not this
one?
Yes, it is works fine with other PCs which do not have dual processor.
(I can not find another machine has dual processor here)
>If so, that suggests to me that there must be either:
>1. A different library on the problem ma
Lin, B (Bill) wrote:
>Does that mean 8.1.3 works fine on other PCs you have, but not this
one?
Yes, it is works fine with other PCs which do not have dual processor.
(I can not find another machine has dual processor here)
Ah, does your problem match what is being discussed here?
http://arch
Yes, It looks exactly same as
http://archives.postgresql.org/pgsql-performance/2006-03/msg00032.php
Only different is: in my case it happens in every 2 mins :)
(I just found it is not only happen during commit, it could be during
other sql call randomly)
Thank you very much, at least I know what
On Tue, Mar 14, 2006 at 11:29:57PM -0500, Tom Lane wrote:
> It's not the easiest sort of problem to debug :-( ...
>
> What I'd try is first letting the problem case run for a bit, then
> stopping it with gdb and dumping out a few Kb of the frontmost memory
> block in the ExecutorState context. S
Joe Sunday <[EMAIL PROTECTED]> writes:
> On Tue, Mar 14, 2006 at 11:29:57PM -0500, Tom Lane wrote:
>> What I'd try is first letting the problem case run for a bit, then
>> stopping it with gdb and dumping out a few Kb of the frontmost memory
>> block in the ExecutorState context. Sometimes, lookin
On Wed, Mar 15, 2006 at 01:10:41PM -0500, Tom Lane wrote:
> Joe Sunday <[EMAIL PROTECTED]> writes:
> > On Tue, Mar 14, 2006 at 11:29:57PM -0500, Tom Lane wrote:
> >> What I'd try is first letting the problem case run for a bit, then
> >> stopping it with gdb and dumping out a few Kb of the frontmo
The following bug has been logged online:
Bug reference: 2313
Logged by: Francisco de Assis Carvalho da Silva Neto
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: Windows XP
Description:Installation on a FAT32 partition
Details:
When ins
The following bug has been logged online:
Bug reference: 2312
Logged by: inner
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.2
Operating system: Windows XP pro
Description:Software caused connection abort (0x2745/10053) with
long Bytea (>4.5mb) in the q
The following bug has been logged online:
Bug reference: 2315
Logged by: Alexander Kirpa
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: FreeBSD 6.0
Description:Crash engine after modify "active" function
Details:
FUNCTION f1(text, int4)
The following bug has been logged online:
Bug reference: 2319
Logged by: Mattias Kregert
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.0
Operating system: Linux 2.4
Description:psql utf8/latin1 client_encoding bug when using '-c'
Details:
Psql '-c' does n
Name: Alexis Wilke
email: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating System: Linux RedHat 9.0
Short Description: problems with renaming a column of type serial
and GRANT/REVOKE instructions in pg_dump
Details:
Hi guys,
I have been working on a database
The following bug has been logged online:
Bug reference: 2317
Logged by: TomasKlockar
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.3.2/7.4.7
Operating system: linux(fedora)
Description:Wrong sorting order for (VW)
Details:
SELECT cname FROM clients ORDER B
The following bug has been logged online:
Bug reference: 2318
Logged by: Mete Akdogan
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3-1
Operating system: win-xp
Description:language
Details:
hi, i am a teaching assistant in www.deu.edu.tr, in one of our d
The following bug has been logged online:
Bug reference: 2316
Logged by: Teofilo Santos
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3
Operating system: Red Hat Enterprise Linux 4
Description:problems when Restore Backup in RHEL4
Details:
I made a pg_dum
The following bug has been logged online:
Bug reference: 2314
Logged by: L.Jumadi
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: SimplyMepis 3.4.3 with kernel 2.6.15.2
Description:The Order changed?
Details:
I have a table named test wi
On Sun, 12 Mar 2006, L.Jumadi wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2314
> Logged by: L.Jumadi
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1.3
> Operating system: SimplyMepis 3.4.3 with kernel 2.6.15.2
> Description:The
On Mon, 13 Mar 2006, TomasKlockar wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2317
> Logged by: TomasKlockar
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 7.3.2/7.4.7
> Operating system: linux(fedora)
> Description:Wrong sorting o
"Alexander Kirpa" <[EMAIL PROTECTED]> writes:
> Description:Crash engine after modify "active" function
I can't reproduce this in HEAD. I think it's probably the same bug
already reported here:
http://archives.postgresql.org/pgsql-bugs/2006-03/msg6.php
and fixed here:
http://archives.
"Mattias Kregert" <[EMAIL PROTECTED]> writes:
> -- ...but this does not.
> % psql -h server mydb -c "set client_encoding to 'latin1'; select * from
> mytable where text='Ã
ÃÃ';"
> ERROR: invalid UTF-8 byte sequence detected near byte 0xc5
There is no hope of that ever working, since the string
"TomasKlockar" <[EMAIL PROTECTED]> writes:
> I think the database was initialized with UTF8 but it might have been
> ISO_8859-1, however the error is easily repeatable and ill be happy to
> provide a dump.
If the database encoding doesn't match the database locale (server
LC_COLLATE setting), all
"Teofilo Santos" <[EMAIL PROTECTED]> writes:
> I made a pg_dumpall in a postgresql server without problems (using Red Hat
> 9. and postgresql 8.0.3), but when i attempt to restore this backup in a
> RHEL4 (kernel 2.6.9-5 64 bits )i receive a lot of erros: invalid command
> \n!
If you're using the
On Tue, Mar 14, 2006 at 09:30:29AM +, Mete Akdogan wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2318
[...]
This is not a bug (and definitely not a PostgreSQL bug ;-)
> hi, i am a teaching assistant in www.deu.edu.tr, in one of our db courses,
> we are plannin
22 matches
Mail list logo