Thread

  1. Storing big chunks of text, variable length

    Thomas Weholt <thomas@cintra.no> — 2001-04-24T15:53:52Z

    Hi,
    
    What would be the most efficient way, performance wise, of storing alot of 
    rather big chunks of text in seperate records in PostgreSQL. I'm dividing 
    huge XML-documents into smaller bits and placing the bits into seperate 
    records. Requests want all or just some of the records, and the document is 
    re-built based on the request. So everything is heavy IO-based.
    
    What would be the best way to do this? LargeObject, the binary blob feature 
    of PostgreSQL or .... ????
    
    The chunks can be everything from a few lines to entire documents of 
    several megabytes ( ok, that's the extreme example, but still .... )
    
    Best regards,
    Thomas
    
    
    
  2. Re: Storing big chunks of text, variable length

    Poul L. Christiansen <poulc@cs.auc.dk> — 2001-04-24T16:07:48Z

    The Text type in PostgreSQL 7.1 can hold up to 1GB of text and AFAIK
    performes quite well.
    
    Previous versions had a text limit of 8-32KB, so upgrade to 7.1, if you
    haven't allready.
    
    HTH,
    Poul L. Christiansen
    
    Thomas Weholt wrote:
    > 
    > Hi,
    > 
    > What would be the most efficient way, performance wise, of storing alot of
    > rather big chunks of text in seperate records in PostgreSQL. I'm dividing
    > huge XML-documents into smaller bits and placing the bits into seperate
    > records. Requests want all or just some of the records, and the document is
    > re-built based on the request. So everything is heavy IO-based.
    > 
    > What would be the best way to do this? LargeObject, the binary blob feature
    > of PostgreSQL or .... ????
    > 
    > The chunks can be everything from a few lines to entire documents of
    > several megabytes ( ok, that's the extreme example, but still .... )
    > 
    > Best regards,
    > Thomas
    > 
    > ---------------------------(end of broadcast)---------------------------
    > TIP 6: Have you searched our list archives?
    > 
    > http://www.postgresql.org/search.mpl