Re: [GENERAL] Quering by Regular Expressions stored in table

Oops, I apoligize for the noise, this does seem to be working. I had an invalid regular expression in the column. Allen Allen Fair wrote: Hi! I have a table with a character column (called match_regex) containing a POSIX regular expression, hoping to have Postgres use it while evaluating the

[GENERAL] Quering by Regular Expressions stored in table

Hi! I have a table with a character column (called match_regex) containing a POSIX regular expression, hoping to have Postgres use it while evaluating the "where" predicate. The following error occurs: SELECT * from patterns where 'blah blah blah' ~ match_regex; ERROR: invalid regular express

Re: [GENERAL] Moving Tablespaces

want to find the best way to plan for when a database outgrows its current server. How about a replication scheme and cutover? If so, is there a preferred replication package to support this? Thanks again! You folks are great, and that makes postgres great! Allen Tom Lane wrote: Allen Fair

Re: [GENERAL] Moving Tablespaces

want to find the best way to plan for when a database outgrows its current server. How about a replication scheme and cutover? If so, is there a preferred replication package to support this? Thanks again! You folks are great, and that makes postgres great! Allen Tom Lane wrote: Allen Fair <[EM

[GENERAL] Moving Tablespaces

Hi! Looking at the "create tablespace " command in the docs, I was wondering how feasible it is to move a database/tablespace to another server/instance of PostgreSQL. Issue: moving databases using pg_dump and pg_restore is more time-consuming than desired, requiring the db to be unavailable

[GENERAL] Moving Tablespaces

Hi! Looking at the "create tablespace " command in the docs, I was wondering how easy it is to move a database/tablespace to another server/instance of PostgreSQL. We have lots of databases, with the same definitions, with 1 database per client account on the server. I can setup the database

Re: [GENERAL] out of memory for query result

From my googling, it seems the Perl DBD driver for Postgres does *not* support the cursor (see below). I hope someone can refute this! I am otherwise looking for code to implement Postgres cursors in Perl. I can not find the "DECLARE CURSOR" defined in the Perl DBI documentation either. Thanks