pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Rob Sargent <robjsargent@gmail.com>
To: Benedict Holland <benedict.m.holland@gmail.com>
To: Joe Carlson <jwcarlson@lbl.gov>
Cc: Mark Dilger <mark.dilger@enterprisedb.com>
Cc: pgsql-general <pgsql-general@lists.postgresql.org>
Subject: Re: TEXT column > 1Gb
Date: Wed, 12 Apr 2023 11:37:18 -0600
Message-ID: <51512362-ab2d-e927-d520-4bd67517273b@gmail.com> (raw)
In-Reply-To: <CAD+mzowRf0w=PST21DZQn8p_=Yzu94WbC3sncBNYS1r5rF=n0A@mail.gmail.com>
References: <85984fc4-6e08-06ad-78d7-d6f73a5c90a0@gmail.com>
	<0A8EB6F5-57BC-4519-8E9A-DBB809CC09D5@lbl.gov>
	<E18E02B1-39DE-4464-9C8C-F0C06BBF771B@enterprisedb.com>
	<A29ABFF1-8014-46B2-9425-34F59812581A@lbl.gov>
	<CAD+mzowRf0w=PST21DZQn8p_=Yzu94WbC3sncBNYS1r5rF=n0A@mail.gmail.com>

On 4/12/23 11:24, Benedict Holland wrote:
> For documents that long I would seriously consider using large objects 
> and refencing them with their OIDs. Text fields get put in a special 
> location within the database. It's similar (possibly exactly) to using 
> large objects. Also, you can potentially compress them to save space 
> on write and read. 1gb of text is a lot of text.
>

I've gone down the premature optimization coded/compressed route and am 
still regretting it. I would either not bother or move to LO as per 
Benedict's suggestion.  The test may come to whether you plan to use 
database features (functions, procedures) to work on the data versus 
feeding it out to the endless list of sequence/genetic analysis tools.   
General compression is robust and fast.  My custom code/comp is likely 
neither :( .










view thread (15+ messages)  latest in thread

Message-ID: <51512362-ab2d-e927-d520-4bd67517273b@gmail.com>
Permalink:  ../51512362-ab2d-e927-d520-4bd67517273b@gmail.com/
Also on:    postgresql.org/message-id/51512362-ab2d-e927-d520-4bd67517273b@gmail.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-general@postgresql.org
  Cc: robjsargent@gmail.com, benedict.m.holland@gmail.com, jwcarlson@lbl.gov, mark.dilger@enterprisedb.com
  Subject: Re: TEXT column > 1Gb
  In-Reply-To: <51512362-ab2d-e927-d520-4bd67517273b@gmail.com>
  References: <85984fc4-6e08-06ad-78d7-d6f73a5c90a0@gmail.com> <0A8EB6F5-57BC-4519-8E9A-DBB809CC09D5@lbl.gov> <E18E02B1-39DE-4464-9C8C-F0C06BBF771B@enterprisedb.com> <A29ABFF1-8014-46B2-9425-34F59812581A@lbl.gov> <CAD+mzowRf0w=PST21DZQn8p_=Yzu94WbC3sncBNYS1r5rF=n0A@mail.gmail.com> <51512362-ab2d-e927-d520-4bd67517273b@gmail.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