pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jan Wieck <JanWieck@Yahoo.com>
To: David Olbersen <DOlbersen@stbernard.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: (long) What's the problem?
Date: Sun, 08 Jun 2003 11:08:25 -0400
Message-ID: <3EE35169.8000706@Yahoo.com> (raw)
References: <E7E213858379814A9AE48CA6754F5ECB0D6EBD@mail01.stbernard.com>

David Olbersen wrote:
> Anybody have any ideas about a problem with this query?
> 
> urldb2=> EXPLAIN
> urldb2-> SELECT
> urldb2->   id,
> urldb2->   source,
> urldb2->   insertedby,
> urldb2->   insertedon,
> urldb2->   priority
> urldb2-> FROM
> urldb2->   indexscan
> urldb2-> WHERE
> urldb2->   lower(
> urldb2->     substring(
> urldb2->       urlhost( source ), rposition( 'www.', urlhost( source ) ) + 2
> urldb2->     )
> urldb2->   ) ~ '^q.*'
> urldb2-> ORDER BY source;                                                                
> 
> QUERY PLAN                                     
> -------------------------------------------------------------------------------------------------------------------------------------------
>  Sort  (cost=23.50..23.50 rows=3 width=48)
>    Sort Key: source
>    ->  Seq Scan on indexscan  (cost=0.00..23.47 rows=3 width=48)
>          Filter: (lower("substring"(urlhost(source), (rposition('www.'::text, (urlhost(source))::character varying) + 2))) ~ '^q.*'::text)
> (4 rows)
> 
> OK, cost=23.50..23.50, should be a quickie. I'll EXPLAIN ANALYZE just to be safe:
> 
> urldb2=> EXPLAIN ANALYZE
> urldb2-> SELECT
> urldb2->   id,
> urldb2->   source,
> urldb2->   insertedby,
> urldb2->   insertedon,
> urldb2->   priority
> urldb2-> FROM
> urldb2->   indexscan
> urldb2-> WHERE
> urldb2->   lower(
> urldb2->     substring(
> urldb2->       urlhost( source ), rposition( 'www.', urlhost( source ) ) + 2
> urldb2->     )
> urldb2->   ) ~ '^q.*'
> urldb2-> ORDER BY source;
> 
> server closed the connection unexpectedly
>         This probably means the server terminated abnormally
>         before or while processing the request.
> The connection to the server was lost. Attempting reset: Failed.

If I would be you I would unlimit the coresize in the environment the 
postmaster is running, eventually recompile with debug symbols enabled 
and look at the stack backtrace of the coredump created when then 
backend crashes.


Jan

-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #




view thread (4+ messages)

Message-ID: <3EE35169.8000706@Yahoo.com>
Permalink:  ../3EE35169.8000706@Yahoo.com/
Also on:    postgresql.org/message-id/3EE35169.8000706@Yahoo.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: JanWieck@Yahoo.com, DOlbersen@stbernard.com
  Subject: Re: (long) What's the problem?
  In-Reply-To: <3EE35169.8000706@Yahoo.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox