pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jan Wieck <JanWieck@Yahoo.com>
To: Mathijs Brands <mathijs@ilse.nl>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Subject: Re: all views in database broken at once
Date: Tue, 27 Mar 2001 04:43:15 -0500 (EST)
Message-ID: <200103270943.EAA26742@jupiter.jw.home> (raw)
In-Reply-To: <20010325191424.A60295@ilse.nl>

Mathijs Brands wrote:
> On Sat, Mar 24, 2001 at 11:36:56PM -0500, Tom Lane allegedly wrote:
> > Mathijs Brands <mathijs@ilse.nl> writes:
> > > How about being able to recompile them (keeping the SQL around in the
> > > system catalogs)? Doesn't Oracle allow you to do something like that?
> >
> > That's another possibility.  It's not real clear that there's any
> > advantage to storing rules in preparsed form to begin with --- if
> > we just stored the original text and reparsed it each time it was
> > read, the system would be vastly more flexible, and probably not
> > noticeably slower.
>
> But every bit of performance counts, of course...

    The  question  is  if parsing the original query is that more
    expensive than converting the printed  node  tree  back  into
    it's  binary representation, what's done now. And then again,
    this is only done  when  the  relation  is  opened  and  it's
    RelationData  not  found  in  the  relcache.  If the relcache
    serves well, this happens once per connection.

    OTOH, due to toast  we  don't  need  to  save  space  in  the
    pg_rewrite tuples any more. Adding two new attributes to hold
    just  the   backparsed   rule   qualification   and   actions
    (backparsed  from  the nodes like done for pg_dump), it might
    be easy to create a utility that recompiles rules -  for  one
    or all relations.


Jan

--

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



_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com




view thread (9+ messages)

Message-ID: <200103270943.EAA26742@jupiter.jw.home>
Permalink:  ../200103270943.EAA26742@jupiter.jw.home/
Also on:    postgresql.org/message-id/200103270943.EAA26742@jupiter.jw.home

 · 

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 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: JanWieck@Yahoo.com, mathijs@ilse.nl, tgl@sss.pgh.pa.us
  Subject: Re: all views in database broken at once
  In-Reply-To: <200103270943.EAA26742@jupiter.jw.home>
  References: <20010325191424.A60295@ilse.nl> <200103270943.EAA26742@jupiter.jw.home>

* 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