From: Tom Lane <tgl@sss.pgh.pa.us>
To: poange@technologist.com
Cc: pgsql-sql@postgresql.org
Cc: pgsql-general@postgresql.org
Cc: pgsql-bugs@postgresql.org
Subject: Re: problem with view and case - please help
Date: Fri, 21 Jul 2000 10:27:07 -0400
Message-ID: <13008.964189627@sss.pgh.pa.us> (raw)
In-Reply-To: <39780EEE.BBCB6406@technologist.com>
References: <39780EEE.BBCB6406@technologist.com>
Ange Michel POZZO <poange@technologist.com> writes:
> CREATE VIEW browser
> AS
> SELECT
> agent_i,
> CASE
> < massive CASE expression >
> ELSE agent_i END AS navigateur, count (agent_i)
> as total from access group by agent_i;
> pqReadData() -- backend closed the channel unexpectedly.
Not sure why you are seeing a crash instead of a complaint, but
there's no chance of making such a huge VIEW expression work in
6.5 --- the rule text won't fit in 8K. Try it in 7.0.2 (which
has still got the 8K limit, but at least it compresses the text).
BTW I tend to agree with the other comment that this seems a clumsy
way to go about it. I'd think about making a table containing a
pattern column and a browser-name column and doing the view as a
join. Might be a little tricky to ensure you get only one match,
however ...
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, poange@technologist.com, pgsql-general@postgresql.org, pgsql-bugs@postgresql.org
Subject: Re: problem with view and case - please help
In-Reply-To: <13008.964189627@sss.pgh.pa.us>
References: <39780EEE.BBCB6406@technologist.com> <13008.964189627@sss.pgh.pa.us>
* 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