EXPLAIN generates a single NOTICE, though it could have many lines...
Like :
brw=# explain select * from customers;
NOTICE: QUERY PLAN:
Seq Scan on customers (cost=0.00..1018.75 rows=17275 width=428)
and then a more complex query :
brw=# explain select * from
customers,inventory,invoice_master,quote_master,quote_line_items;
NOTICE: QUERY PLAN:
Nested Loop (cost=0.00..655655853.05 rows=9909199125 width=1245)
-> Nested Loop (cost=0.00..375370.55 rows=5441625 width=1076)
-> Nested Loop (cost=0.00..48.05 rows=315 width=648)
-> Nested Loop (cost=0.00..6.75 rows=35 width=464)
-> Seq Scan on invoice_master (cost=0.00..1.05 rows=5
width=427)
-> Seq Scan on quote_line_items (cost=0.00..1.07
rows=7 width=37)
-> Seq Scan on quote_master (cost=0.00..1.09 rows=9
width=184)
-> Seq Scan on customers (cost=0.00..1018.75 rows=17275 width=428)
-> Seq Scan on inventory (cost=0.00..102.21 rows=1821 width=169)
EXPLAIN
-Mitch
----- Original Message -----
From: "Marc Sherman" <msherman@projectile.ca>
To: <pgsql-php@postgresql.org>
Cc: <dirk@rackspace.com>
Sent: Friday, May 25, 2001 2:37 PM
Subject: RE: [PHP] Re: Printing Notices to the web?
> From: pgsql-php-owner@postgresql.org
> > :
> > : Your hero has come :-) The pg_last_notice() function is
> > : scheduled to be released in PHP 4.0.7 . Read more about it
> > : here: http://www.php.net/bugs.php?id=9541&edit=1
>
> Is this adequate for cases where a single query generates more
> than one notice message? Don't explains generate a large number
> for each query?
>
> - Marc
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
