ed strace output of collector is attached. Unfortunately, the
server wasn't very busy (just 10-20% utilization).
The stats_command_string was disabled during stracing.
Thanks in advance
--
Marcin
collector.txt.gz
Description: GNU Zip compressed data
---(end of broadc
of pgstat in last six hours was 8.5 MB.
--
Marcin
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
have to wait for 8.2?
Thanks again for a great help,
--
Marcin
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
Dear Sirs,
[This is in a way a reiteration of Marcin Zukowski's report of 19 Jan 2001
http://pgsql.service.net.pl/mhonarc/pgsql-bugs/2001-01/msg00110.html
which was ignored because of a somewhat unfortunate test case.]
I have created a new database and then have run
Tom Lane <[EMAIL PROTECTED]> writes:
> Marcin Wolinski <[EMAIL PROTECTED]> writes:
> > After this the 'w' class contains 116170 rows. For each value of wfid
> > there are no more than 7584 different values of wnr (with median of 1
> > value per wfi
vide my bug-report). Is this OK?
Personaly, I would like postgres to define compilation-definable null
compare method ( or at least use some constant method ).
Ofcourse, these methods couldn't be used in WHERE clauses, but for sorting
it could prove useful.
Or maybe I&
with null BIGGER than everything.
I really think it's a bug.
Please let me know, what do you think about it, and please make it go to
the pgsql-bugs, because my mails aren't accepted there. I didn't get any
reply for my previous letter, and I don't know what to think.
best
inity for null
values (but I really don't like it :) ). I still think pgsql is not
compliant with SQL92, but I'm not the one to decide if it should be
changed.
Best regards
Marcin Zukowski
---(end of broadcast)---
TIP 3: if posting/reading
The following bug has been logged online:
Bug reference: 2804
Logged by: Marcin Waldowski
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.5
Operating system: Windows XP SP2 (polish version)
Description:Incorrect encoding of comment in backup of UTF8 database
The following bug has been logged online:
Bug reference: 3242
Logged by: Marcin Waldowski
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.3 and 8.2.1
Operating system: Windows XP SP2
Description:FATAL: could not unlock semaphore: error code 298
Details
We've made some tests on Linux and it seems like it never happen on this
platform, but we use 8.1, not 8.2.
select version()
PostgreSQL 8.1.3 on i686-pc-linux-gnu, compiled by GCC
i686-pc-linux-gnu-gcc (GCC) 3.4.5 (Gentoo 3.4.5, ssp-3.4.5-1.0, pie-8.7.9)
Regards, Marcin
Marcin Wald
osoft.com/en-us/library/ms685071.aspx) which is
executed from PGSemaphoreUnlock, was executed one time more than needed.
I'm afraid than problem may lie above win32_sema.c :(
Regards, Marcin
Marcin Waldowski wrote:
The following bug has been logged online:
Bug reference: 3242
Logged
date operations. What is strange we cannot reproduce this
problem on Linux. But we can do this on Windows. What another
information should we provide?
Regards, Marcin
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send
ise that might not
be easy for a problem like this :-)
Our test case is our application, but unfortunately I cannot send it to
you. I will think about test case, but I need to find a time for writing
it :( I can reproduce error and provide all information you need from
PostgreSQL. Please ins
Marcin Waldowski wrote:
Doesn't the postmaster restart all other backends due to the FATAL
error?
Are you saying that you can no longer make new connections to the
server,
or is the problem coming from that the aplpication doesn't like that the
server kicked out all connections?
n says nothing about a limit - I'm sure it's just a 32-bit
counter in the kernel). I'll give that a shot.
Magnus, Tom, thank you for finding what causes the problem :) I hope
that was also a reason why other transactions were hung (because that is
a prior, I think).
Marcin -
The following bug has been logged online:
Bug reference: 3242
Logged by: Marcin Waldowski
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.3 and 8.2.1
Operating system: Windows XP SP2
Description:FATAL: could not unlock semaphore: error code 298
Details
confirm that this fix works. We will also leave test running
for the night to be absolutely sure that it's ok. I will inform you
about the result.
Thanks again, Marcin
---(end of broadcast)---
TIP 6: explain analyze is your friend
Ok, that&
Tom Lane wrote:
Marcin Waldowski <[EMAIL PROTECTED]> writes:
Ok, that's the end of the story :) My workmate has confirmed that during
night test PostgreSQL worked perfectly :)
That fix was Obviously Necessary even without testing -- you're being
too conservative about
CT 1875::float/1000.0;
?column?
--
1.875
(1 row)
qurczak=# SELECT (1875/1000.0)::float;
float8
1.875
(1 row)
It works ;] You try something this int/float = yee khmm but
int::float/float= float, or something like this ;]
--
"Nieobecni nie mają rac
Hi
sorry for my english
My serwer is:
p4 2.4 Ghz, 1 GB RAM, data from postgres on RAID 0 SCSI
(hardware scsi)
some tables (about 15) have 50.000 position, and all data (pgdumpall) are
about 600 MB
I have apache 1.3.29 - and he use the database for generate pages.
So my problem is performance thi
The following bug has been logged on the website:
Bug reference: 6327
Logged by: Marcin Kasperski
Email address: marcin.kasper...@mekk.waw.pl
PostgreSQL version: 9.1.1
Operating system: Linux
Description:
Synopsis
=
'goog:*' matches google.com
b
22 matches
Mail list logo
