From: wieck@debis.com
To: pd3@wuerl.wustl.edu
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [SQL] rule plan too big (fwd)
Date: Thu, 3 Jun 1999 18:24:41 +0200 (MET DST)
Message-ID: <m10paIL-0003kGC@orion.SAPserv.Hamburg.dsh.de> (raw)
In-Reply-To: <Pine.SOL.4.02.9906031056490.29662-100000@wuerl.wustl.edu>
> I'm trying to create a relatively large view and I'm getting the
> "DefineQueryRewrite: rule plan too big" error. Is this a bug in Postgres
> that currently has no workaround, or is there something I can do. A
> previous posting mentioned changing the blocksize. I thought I made this
> change correctly, but it did not get rid of the error. Any help would be
> much appreciated.
Currently there is no other workaround than increasing the
overall database blocksize until it fits. At the time I
mentioned changing the rule plan (and qualification) storage
to be able to split over tuples there was discussion about a
general tuple split capability, which would have solved this
problem silently. Unfortunately this general solution did not
incarnate for v6.5.
I've also played around with another data type which uses an
internal format that is a simple, byte oriented lz
compression. Using that on rule strings approximately
compresses with rates of 40-70% (better on large rules ==
complex views).
For now I'm planning to wait until v6.5 is released and then
make a feature patch where the rule plans will be stored
compressed. That will lower the problem (not entirely fixing
it) and offer the new compressed type for other purposes too.
*******************************************************
* WE STILL NEED THE GENERAL TUPLE SPLIT CAPABILITY!!! *
*******************************************************
I vote for sticking this onto the TODO and make it a
permanent show-stopper for version 7.0. NO v7.0 without
unlimited tuple size! I know that this is about a year or so
ahead :-)
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#========================================= wieck@debis.com (Jan Wieck) #
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: wieck@debis.com, pd3@wuerl.wustl.edu
Subject: Re: [SQL] rule plan too big (fwd)
In-Reply-To: <m10paIL-0003kGC@orion.SAPserv.Hamburg.dsh.de>
References: <Pine.SOL.4.02.9906031056490.29662-100000@wuerl.wustl.edu> <m10paIL-0003kGC@orion.SAPserv.Hamburg.dsh.de>
* 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