pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jan Wieck <janwieck@Yahoo.com>
To: Hannu Krosing <hannu@tm.ee>
Cc: Alexaki Sofia <alexaki@ics.forth.gr>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Re: [SQL] improve performance
Date: Tue, 16 Jan 2001 14:33:03 -0500 (EST)
Message-ID: <200101161933.OAA11693@jupiter.jw.home> (raw)
In-Reply-To: <3A631A7C.922EAEAC@tm.ee>

Hannu Krosing wrote:
> Tom Lane wrote:
> >
> >
> > I've heard lots of people want to increase BLCKSZ, but you're the first
> > one who ever wanted to reduce it.  You sure you want to do this?  It's
> > going to make the maximum row length uncomfortably short.
>
> And it may even not work, as some system tables (that are also affected
> by this)
> may need the full 8k. AFAIK it has never been tested with BLCKSZ < 8k

    Except  for  two different sorted (but correct) results while
    selecting inherited tables in "misc", regression tests passed
    with 2K.

    Why  shouldn't  it work? All the catalogs that require really
    big data have toast tables now.

    Anyway, the 8K default BLCKSZ already restricts index  tuples
    to 2700 bytes.  So I wouldn't recommend it at all.


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 (5+ messages)

Message-ID: <200101161933.OAA11693@jupiter.jw.home>
Permalink:  ../200101161933.OAA11693@jupiter.jw.home/
Also on:    postgresql.org/message-id/200101161933.OAA11693@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 using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: janwieck@Yahoo.com, hannu@tm.ee, alexaki@ics.forth.gr, tgl@sss.pgh.pa.us, pgsql-sql@postgresql.org
  Subject: Re: Re: [SQL] improve performance
  In-Reply-To: <200101161933.OAA11693@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