The following bug has been logged online:
Bug reference: 2075
Logged by: Arjen
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.0
Operating system: Gentoo linux (2.6.11 kernel)
Description:Strange choice of bitmap-index-scan
Details:
I haven't tr
The following bug has been logged online:
Bug reference: 4769
Logged by: Arjen Nienhuis
Email address: a.g.nienh...@gmail.com
PostgreSQL version: 8.3.7
Operating system: Ubuntu 8.10 and 9.04
Description:xmlconcat produces invalid xml values -> data corruption
Deta
The following bug has been logged online:
Bug reference: 3031
Logged by: Arjen van der Meijden
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.1
Operating system: Debian Linux (etch, 2.6.17 kernel)
Description:PHP (and others?) cannot close a connection when
On 20-2-2007 4:42 Tom Lane wrote:
"Arjen van der Meijden" <[EMAIL PROTECTED]> writes:
I'm not sure whether this is a php-issue or a postgresql-client-api one, but
when connecting gdb to that process and doing a 'bt' it displays:
#0 0xa7c36d9f in free () from /l
ething like this
while-loop, they need to request the result-status and if its not the
result of a finished query (either failed, ok, empty, etc) they should
send a cancel request?
Anyway, I'll add your advice to that bug-report.
Best regards,
Arjen
---(end of b
c.relname ~ '^pwprijs$'
ORDER BY 2, 3;
I shut down the postgresql-server after the restart again to prevent
further changes to the data-files of it.
Best regards,
Arjen van der Meijden
---(end of broadcast)---
TIP 3: Have you c
On 13-9-2005 20:04, Tom Lane wrote:
Arjen van der Meijden <[EMAIL PROTECTED]> writes:
On 13-9-2005 16:25, Tom Lane wrote:
Well, its an index, not a table. It was the index:
"pg_class_relname_nsp_index" on pg_class(relname, relnamespace).
Ah. So you've reindexed p
On 13-9-2005 20:53, Tom Lane wrote:
Arjen van der Meijden <[EMAIL PROTECTED]> writes:
Unless reindexing is part of other commands, I didn't do that. The last
time 'grep' was able to find an reference to something being reindexed
was in June, something (maybe me, but
On 13-9-2005 23:01, Tom Lane wrote:
Arjen van der Meijden <[EMAIL PROTECTED]> writes:
That's all? There's something awfully suspicious about that. You're
sure this is 8.0.3?
When I do "select version();"
PostgreSQL 8.0.3 on i686-pc-linux-gnu, compiled by
Arjen van der Meijden wrote:
On 13-9-2005 23:01, Tom Lane wrote:
I'll try and see if I can dig up more from the logs and see if I can
test a few reasonable scenario's tomorrow though.
I wasn't able to find anything suspicious at all. A smart-shutdown
should've come fr
Tom Lane wrote:
Arjen van der Meijden <[EMAIL PROTECTED]> writes:
I'll try and see if I can dig up more from the logs and see if I can
test a few reasonable scenario's tomorrow though.
I wasn't able to find anything suspicious at all.
Is it conceivable that the i
On 13-9-2005 0:26, Tom Lane wrote:
Arjen van der Meijden <[EMAIL PROTECTED]> writes:
There is still the question of how the LSN value got corrupted, but
we've probably missed any chance of finding that out now.
As a matter of fact, I just tested it again. Issuing that same query
w
On 13-9-2005 16:25, Tom Lane wrote:
Arjen van der Meijden <[EMAIL PROTECTED]> writes:
It's highly unlikely that that query has anything to do with it, since
it's not touching anything but system catalogs and not trying to write
them either.
Indeed, other things trigger it as w
e fraction of zichtbaar's is small
enough. With 1 and 8 as false, it happens, with 27 as false its not
happening.
Best regards,
Arjen
Tom Lane wrote:
"Arjen" <[EMAIL PROTECTED]> writes:
-> BitmapAnd (cost=5.62..5.62 rows=1 width=0)
-> Bitmap Index
Tom Lane wrote:
Arjen van der Meijden <[EMAIL PROTECTED]> writes:
I found another example, in case you're interested:
Did you apply the patch?
No, it was just another test-case I stumbled upon. And I'd rather nog
install development versions of postgresql on the machine
btree (tabelid) WHERE tabel = 'n'::bpchar
(yes, I'm trying to figure out the best index combinations here ;-) )
Either of the two selected indexes is useable, but the
pwproduktrel_tabelid_meuk is obviously (much?) smaller in size and
therefore faster to look in, isn't it?
The
The following bug has been logged online:
Bug reference: 2441
Logged by: Arjen van der Meijden
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2devel, 05-16
Operating system: Solaris 10
Description:All useable indexes for an IN are used, not just one
Details
17 matches
Mail list logo
