Skip site navigation (1) Skip section navigation (2)

Re: text parsing function

From: John DeSoi <desoi(at)pgedit(dot)com>
To: KeithW(at)narrowpathinc(dot)com
Cc: "PostgreSQL Novice" <pgsql-novice(at)postgresql(dot)org>
Subject: Re: text parsing function
Date: 2005-04-19 03:11:33
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-novice
On Apr 18, 2005, at 11:41 AM, Keith Worthington wrote:

> I am trying to create software that will parse a string of 
> varchar(160) and
> write different parts of it into various locations in a database.
> My thought process is something like this.
> Create one or more functions to parse the data.
> Create a trigger function that calls parsing function(s) and writes 
> the data
> into the appropriate locations.
> Create after trigger on table that contains the entire string.

You could also use the COPY command to copy the unparsed data to a 
temporary table (one text column) and then call a function to parse the 
rows in the temporary table. The pgEdit distribution has an example of 
this for processing HTTP logs.

> I have written the first function using pl/pgsql.  As one might expect 
> text
> processing in pl/pgsql is messy.

> Unfortunately I do not know Perl which is probably better suited to 
> the text
> munging part of my problem.  Is there any penalty for using pl/pgsql 
> for this
> function?  Given the inputs below does anyone see a problem with my 
> code?  Can
> anyone suggest a better course of action?

I have not done any benchmarks or optimization, but text processing in 
psql seems relatively slow.

John DeSoi, Ph.D.
Power Tools for PostgreSQL

In response to

pgsql-novice by date

Next:From: Michael FuhrDate: 2005-04-19 03:29:59
Subject: Re: inset html data into text column
Previous:From: John DeSoiDate: 2005-04-19 02:55:23
Subject: Re: Windows XP PostgreSQL usage

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group