Re: [GENERAL] Event trigger information accessibility on plpgsql

2013-07-30 Thread Javier de la Torre
Jul 29, 2013, at 9:02 PM, Andrew Tipton wrote: > On Mon, Jul 29, 2013 at 10:08 PM, Javier de la Torre > wrote: > You think it will be possible to, instead of comparing schemas, looking for > the last modified OID on the DB to figure out where it happened? > > Not really. W

Re: [GENERAL] Event trigger information accessibility on plpgsql

2013-07-29 Thread Javier de la Torre
Thanks Andrew, You think it will be possible to, instead of comparing schemas, looking for the last modified OID on the DB to figure out where it happened? On Jul 29, 2013, at 3:42 PM, Andrew Tipton wrote: > On Mon, Jul 29, 2013 at 9:12 PM, Javier de la Torre > wrote: > Hi, &

[GENERAL] Event trigger information accessibility on plpgsql

2013-07-29 Thread Javier de la Torre
. But would it be possible to do a plpgsql trigger where I have access to the table name and OID when I do an ALTER table to rename a column? Right now it feels i can only know that a table has been altered, but not which one Thanks in advance. Javier de la Torre @jatorre CartoDB 148 Lafayette St

Re: [GENERAL] Move db files from one pgsql instance to another

2006-08-16 Thread Javier de la Torre
site that will be lost... well, I can backup this one without ptoblems and reinsert it after. Thanks again. Javier. On 8/16/06, Jeff Davis <[EMAIL PROTECTED]> wrote: On Wed, 2006-08-16 at 20:04 +0200, Javier de la Torre wrote: > I am working right now in an strategy to improve the pe

[GENERAL] Move db files from one pgsql instance to another

2006-08-16 Thread Javier de la Torre
Hi, I am working right now in an strategy to improve the performance on my server. The situation is this: I have a very large database that it is only update once a month, but when is updated I have to process a lot of things on the data to create caches, aditional tables, etc. The processing o

Re: [GENERAL] psql is slow and it does not take much resources

2006-05-03 Thread Javier de la Torre
Great! Then there will be no problems. I would use COPY but I think I can not. While moving from MySQL to PostgreSQL I am also transforming a pair of fields, latitude, longitude, into a geometry field, POINT, that is understood for Potgis. I though I will not be able to use COPY when inserting da

Re: [GENERAL] psql is slow and it does not take much resources

2006-05-03 Thread Javier de la Torre
wrote: On Wednesday 03 May 2006 16:12, Larry Rosenman wrote: >Javier de la Torre wrote: >> It is inserts. >> >> I create the inserts myself with a Python programmed I hace created >> to migrate MySQL databases to PostgreSQL (by th way if someone wants >> it...) > &g

Re: [GENERAL] psql is slow and it does not take much resources

2006-05-03 Thread Javier de la Torre
It is inserts. I create the inserts myself with a Python programmed I hace created to migrate MySQL databases to PostgreSQL (by th way if someone wants it...) Thanks. Javier. On 5/3/06, Larry Rosenman <[EMAIL PROTECTED]> wrote: Javier de la Torre wrote: > Hi all, > > I&#x

[GENERAL] psql is slow and it does not take much resources

2006-05-03 Thread Javier de la Torre
Hi all, I've been searching around for an answer to this, but I coulnd't find anything. So here we go. I am running PostgreSQL 8.1.3 on Red Hat on an Intel server with 2GB of RAM and lot of free HD space. I have a very large dump file, more then 4GB, to recreate a database. When I run: psql -U