Re: [HACKERS] type coerce problem with lztext - Mailing list pgsql-hackers

From wieck@debis.com (Jan Wieck)
Subject Re: [HACKERS] type coerce problem with lztext
Date
Msg-id m12PApo-0003kGC@orion.SAPserv.Hamburg.dsh.de
Whole thread Raw
In response to Re: [HACKERS] type coerce problem with lztext  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: [HACKERS] type coerce problem with lztext  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: [HACKERS] type coerce problem with lztext  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Bruce Momjian wrote:

> We clearly needed this for 7.0 because of the larger plans.  Good thing
> Jan had it available, becuase I can imagine some major headaches for
> people without it.
   I  haven't  had  it available. But where able to dig out some   revision numbers, then take some CVS  diffs,  and
reactivate  two files from the CVS Attic directories.
 
   Here's something close to the new limit:
       rulename    | length | octet_length   ----------------+--------+--------------    _RETv1         |  64677 |
  7440
 
   The  view v1 is a simple 'SELECT * FROM t1' and t1 is a table   of 220 columns with the same names and types  as
nearly all   attributes of the system catalogs. Makes me feel comfortable.
 


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) #




pgsql-hackers by date:

Previous
From: wieck@debis.com (Jan Wieck)
Date:
Subject: Re: [HACKERS] type coerce problem with lztext
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] type coerce problem with lztext