pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jan Wieck <janwieck@Yahoo.com>
To: Poul L. Christiansen <plc@faroenet.fo>
Cc: Keith Wong <keith@e-magine.com.au>
Cc: pgsql-sql@postgresql.org
Subject: Re: 8K Limit, whats the best strategy?
Date: Mon, 21 Aug 2000 10:41:08 -0500 (EST)
Message-ID: <200008211541.KAA02852@jupiter.greatbridge.com> (raw)
In-Reply-To: <399982B7.69A41FA4@faroenet.fo>

Poul L. Christiansen wrote:
> I've just split the text up (in 8 pieces), so it fits into 8K rows. But thats
> only a viable solution if your text is less than a couple of 100K's.
>
> You could try to be a daredevil and use the Toast code, even if it's beta. But
> I don't know how far the Toast project has come.

    TOAST  is  finished  and will be shipped with 7.1. It's not a
    solution for huge items, but medium sized  text  up  to  some
    hundred K works fine.


Jan

>
> Keith Wong wrote:
>
> > Hi everyone,
> >
> > Just wondering what strategies people have used to get around the 8K row
> > limit in Postgres.
> > If anyone has been troubled by this limitation before and has a nice
> > solution around it, I would love to hear it.
> >
> > My application is a web-based system in which needs to store large amounts
> > of text.
> > The text stored needs to searchable as well.
> >
> > Cheers,
> > Keith.
>


--

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





view thread (7+ messages)  latest in thread

Message-ID: <200008211541.KAA02852@jupiter.greatbridge.com>
Permalink:  ../200008211541.KAA02852@jupiter.greatbridge.com/
Also on:    postgresql.org/message-id/200008211541.KAA02852@jupiter.greatbridge.com

 · 

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, plc@faroenet.fo, keith@e-magine.com.au
  Subject: Re: 8K Limit, whats the best strategy?
  In-Reply-To: <200008211541.KAA02852@jupiter.greatbridge.com>
  References: <399982B7.69A41FA4@faroenet.fo> <200008211541.KAA02852@jupiter.greatbridge.com>

* 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