pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Hiroshi Inoue <Inoue@tpf.co.jp>
To: Jan Wieck <wieck@debis.com>
Cc: pgsql-sql@postgresql.org
Cc: Philippe Gobin <philippe.gobin@fth.net>
Subject: RE: TOAST (was: BLOB)
Date: Fri, 21 Apr 2000 15:50:48 +0900
Message-ID: <003501bfab5d$ece98b60$2801007e@tpf.co.jp> (raw)
In-Reply-To: <m12hy1L-0003knC@orion.SAPserv.Hamburg.dsh.de>

> -----Original Message-----
> From: pgsql-sql-owner@hub.org [mailto:pgsql-sql-owner@hub.org]On Behalf
> Of Jan Wieck
> 
> > Hello
> >
> > I would like to know
> > - how to create under psql a BLOB field in sql language
> > - how store a value (and not a file) in sql language
> > - the maximum size of the BLOB field
> 
>     For  now  (and  7.0),  there  is no way to have rows >8K in a
>     regular table.
> 
>     But I'm actually making alot  of  progress  in  breaking  it.
>     Seems we'll get rid of this restriction in 7.1.
> 
>     To share some info with the other developers:
> 
>     I  experienced  some  trouble  with   occational   "Deadlock"
>     detections,  when  using  multiple processes hammering on the
>     toaster. But I was able to reproduce the same  error  with  a
>     plain  7.0  and  "text"  attributes (only far less frequent).
>     Seems there's  something  wrong  in  our  deadlock  detection
>     algorithm.
>

Does the trouble mean that "Deadlock" message was issued for
non-deadlock cases ?
  
>     Another  thing  is,  that  ISTM  that index's never shrink on
>     vacuum. One requirement of TOAST  is,  that  the  secondaries
>     tables  index-OID is remembered in the external reference, so
>     the ref can be  passed  around  in  the  entire  backend  and
>     whenever needed, it's real value can be fetched quickly by an
>     index scan. Thus, it's not possible to drop/recreate an index
>     on that right now. Seems we need a "REBUILD INDEX" utility or
>     the like.
>

REINDEX command could do it in a sense.
However current implementation couldn't guarantee the existence
of  proper index in case of abort. Proper implementation would
require the standard transactional control mechanism to handle
relation files such as new naming rule of relation files....

Regards.

Hiroshi Inoue
Inoue@tpf.co.jp 



view thread (13+ messages)  latest in thread

Message-ID: <003501bfab5d$ece98b60$2801007e@tpf.co.jp>
Permalink:  ../003501bfab5d$ece98b60$2801007e@tpf.co.jp/
Also on:    postgresql.org/message-id/003501bfab5d$ece98b60$2801007e@tpf.co.jp

 · 

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: Inoue@tpf.co.jp, wieck@debis.com, philippe.gobin@fth.net
  Subject: Re: TOAST (was: BLOB)
  In-Reply-To: <003501bfab5d$ece98b60$2801007e@tpf.co.jp>
  References: <m12hy1L-0003knC@orion.SAPserv.Hamburg.dsh.de> <003501bfab5d$ece98b60$2801007e@tpf.co.jp>

* 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