Re: [BUGS] query very slow when enable_seqscan=on

2006-07-03 Thread Simon Riggs
On Mon, 2006-07-03 at 22:31 +0200, Tomasz Ostrowski wrote: > I have a very slow query when enable_seqscan=on and very fast when > enable_seqscan=off. My schema looks like this (relevant columns > only): > PS. Actual table and column names are different (they're in Polish) > but I've translated them

Re: [BUGS] query very slow when enable_seqscan=on

2006-07-03 Thread Tom Lane
Tomasz Ostrowski <[EMAIL PROTECTED]> writes: > I have a very slow query when enable_seqscan=on and very fast when > enable_seqscan=off. Here's your problem: > -> Seq Scan on organization (cost=0.00..480.95 rows=1 width=4) > (actual time=0.071..69.702 rows=1892 loops=1) >

Re: [BUGS] BUG #2510: ERROR: out of memory DETAIL: Failed on request of size 825242672.

2006-07-03 Thread Tom Lane
"alex tsai" <[EMAIL PROTECTED]> writes: > I'm having a trouble trying to insert a tuple. > I'm getting this kind of error "ERROR: out of memory DETAIL: Failed on > request of size 825242672". > What could it be? You haven't really provided enough info to let anyone help you, but sometimes this s

[BUGS] query very slow when enable_seqscan=on

2006-07-03 Thread Tomasz Ostrowski
I have a very slow query when enable_seqscan=on and very fast when enable_seqscan=off. My schema looks like this (relevant columns only): create table organizations ( organization_id serial primary key, organization varchar(200) not null, organization_location varchar(55) n

Re: [BUGS] BUG #2511: violation of primary key on update with 2

2006-07-03 Thread Simon Riggs
On Mon, 2006-07-03 at 11:14 +, james wrote: > i think it's a bug in postgresql ... Primary Key constraints are not deferrable currently. This is a known situation so this isn't a bug. I would advise you not to update the PK of your tables. That usually represents a modelling problem and so I

Re: [BUGS] BUG #2507: Problem using two-phase commit

2006-07-03 Thread Nestor Ramirez (Speedy)
Alvaro: I mean that as two-phase commit in the case is used of wanting to update tie tables with dblink, that is to say, that do not esten in my trasaccional scheme. in addition, all operation that becomes after doing "prepare transaction" which it is of update of data base is not included in

[BUGS] BUG #2511: violation of primary key on update with 2 tables

2006-07-03 Thread james
The following bug has been logged online: Bug reference: 2511 Logged by: james Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1.1 Operating system: windows xp professional sp2 Description:violation of primary key on update with 2 tables Details: hi, i've tr

[BUGS] BUG #2510: ERROR: out of memory DETAIL: Failed on request of size 825242672.

2006-07-03 Thread alex tsai
The following bug has been logged online: Bug reference: 2510 Logged by: alex tsai Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1.4 Operating system: FreeBSD 6.1 stable Description:ERROR: out of memory DETAIL: Failed on request of size 825242672. Details: