On Sep 24, 2006, at 8:59 AM, Tom Lane wrote:
Casey Duncan <[EMAIL PROTECTED]> writes:
seed | st_id | 164656
I ran analyze after this, but the results were roughly the same.
What's the statistics target set to, and did you try increasing it?
Can we see the
that column.
Thanks
-Casey
On Sep 23, 2006, at 3:17 PM, Tom Lane wrote:
Casey Duncan <[EMAIL PROTECTED]> writes:
select st_id, min(seed_id) as "initial_seed_id", count(*) as
"seed_count" from see
On Sep 19, 2006, at 1:51 AM, Simon Riggs wrote:
On Mon, 2006-09-18 at 14:08 -0700, Casey Duncan wrote:
I've reported variants of this in the past, but this case is entirely
repeatable.
Executing this query:
select st_id, min(seed_id) as "initial_seed_id", count(*) as
"s
I've reported variants of this in the past, but this case is entirely
repeatable.
Executing this query:
select st_id, min(seed_id) as "initial_seed_id", count(*) as
"seed_count"
from seed group by st_id;
The query plan and table stats are:
QUERY PLAN
On May 11, 2006, at 4:42 AM, Simon Riggs wrote:
On Wed, 2006-05-10 at 09:34 -0700, Casey Duncan wrote:
The script actually fails before the function is even defined anyhow,
on this statement:
INSERT INTO ss
(ss_id, name, ll_id, shared_ss_id, time_added,
shared_creator_id)
SELECT
On May 9, 2006, at 9:09 PM, Tom Lane wrote:
"Casey Duncan" <[EMAIL PROTECTED]> writes:
CREATE FUNCTION write_error_trigf() RETURNS trigger AS '
BEGIN
RAISE EXCEPTION ''Writes not allowed to this table on this
node'';
END;
' LAN
The following bug has been logged online:
Bug reference: 2428
Logged by: Casey Duncan
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: Debian Linux (2.6.13.1-20050914 #2 SMP) 2xOpteron 8GB
RAM
Description:ERROR: out of memory, running
I have the following query which ran fine on 7.4 and fails
consistently now that I've upgraded to 8.1.3. Here is the query and
the plan (I can't explain analyze because of the memory error):
prod=> explain select count(*) from
prod-> (select st_id from sd
prod(>group by st_id having cou
Here's another memory error I can reliably reproduce on postgres
8.1.3. This is on a different server, but with the same postgresql
config as my previous report. It was running a script to upgrade a
snapshot of a production database to the latest schema version for
testing. Eventually we wi
