[GENERAL] Transactions across multiples databases

Hello: I need to modify diferent tables in multiples databases in one transaction. Can i do it whitout lost integrity in all databases if "rollback" is executed? Thanks, Sergio Pili ---(end of broadcast)--- TIP 1: subscribe and unsubscribe command

Re: [GENERAL] Upgrading to 7.3.4?

On Thu, 31 Jul 2003, Paul Ramsey wrote: > Voot! Not necessary! :) > This is a minor version upgrade, so data can remain in place. For a 7.2 > -> 7.3 upgrade you would have to dump-and-restore. > My upgrade procedure is: > tar xvfz postgresql-7.3.4.tar.gz ; cd postgresql-7.3.4 > ./configure ; make

Re: [GENERAL] OSCON "paper"

On Thursday 31 July 2003 17:40, Andrew Sullivan wrote: > Hi, > > I had a couple of requests for copies of my presentation at OSCON. I > don't really know that it's of any value to anyone, but if you'd > like to see a cleaned-up (i.e. you can read it) version of my notes > for that presentation, it

Re: [GENERAL] surppressing column names in COPY format

Robert Treat <[EMAIL PROTECTED]> writes: > the problem is that I am restoring the data to a database with different > column names, which errors out in 7.3 (but didn't under 7.2 since it > didn't produce column names in the COPY output). I checked the docs and > it provided no clue as to how to sup

Re: [GENERAL] Upgrading to 7.3.4?

Thanks for all your suggestions, I will be trying this... :) BTJ On Thu, 2003-07-31 at 20:27, scott.marlowe wrote: > On Thu, 31 Jul 2003, Paul Ramsey wrote: > > > Voot! Not necessary! :) > > This is a minor version upgrade, so data can remain in place. For a 7.2 > > -> 7.3 upgrade you would ha

[GENERAL] surppressing column names in COPY format

in 7.2 doing a data only dump (pg_dump -a -x db > dump) would give output like: UPDATE "pg_class" SET "reltriggers" = 0 WHERE "relname" = 'status'; COPY "status" FROM stdin; 0 INFO 1 WARNING 2 CRIT \. -- Enable triggers UPDATE pg_class SET reltriggers = (SELECT count(*) FROM pg

Re: [GENERAL] Upgrading to 7.3.4?

Voot! Not necessary! :) This is a minor version upgrade, so data can remain in place. For a 7.2 -> 7.3 upgrade you would have to dump-and-restore. My upgrade procedure is: tar xvfz postgresql-7.3.4.tar.gz ; cd postgresql-7.3.4 ./configure ; make ; make install pg_ctl stop ; pg_ctl start Freddy Me

Re: [GENERAL] Postgres Hanging on Inserts

> Alvaro Herrera Munoz <[EMAIL PROTECTED]> writes: > > On Wed, Jul 30, 2003 at 01:03:55PM -0500, Adam Kavan wrote: > >> I have found the problem (I think) below is the list of all the locks > >> pending on the relation. The relation is a hash index on the table that is > >> being INSERT'd rapidly.

[GENERAL] OSCON "paper"

Hi, I had a couple of requests for copies of my presentation at OSCON. I don't really know that it's of any value to anyone, but if you'd like to see a cleaned-up (i.e. you can read it) version of my notes for that presentation, it's available at . A --

Re: [GENERAL] PostgreSQL Question

On Thu, Jul 31, 2003 at 11:52:42AM +0800, Ryan F. Bayhonan wrote: > Hi Patrick, > > Have read your reply in the web about postgreSQL. > (http://archives.postgresql.org/pgsql-interfaces/2001-01/msg00170.php) > > My name is Ryan, and I would like to ask some help about PostgreSQL. > > I have the r

Re: [GENERAL] Updating from update trigger

Answering my own half-way thought solution: of course you won't avoid the infinite loop if you take the location info in a separate table, cause if you do, then you can't update the location by just updating the cd table. So having this solution invalid, I just can think of using some query rewriti

Re: [GENERAL] Updating from update trigger

You should probably rethink the application logic. If there's no way to do it differently, you might be able to place the location details in a separate table, and update them there - this way on update of the "cd" table you will update also the "cd_locations" table, avoiding the loop. You should

Re: [GENERAL] Updating from update trigger

Is there anyone who has a solution to this problem? Greetings, Jonathan Mezach aka Taz News Writer for HL2Zone (www.hl2zone.net) -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Jonathan Mezach Verzonden: vrijdag 25 juli 2003 21:07 Aan: [EMAIL PROTECTED]

Re: [GENERAL] CREATE TABLE with a column of type {table name}

On Thu, 31 Jul 2003, Ang Chin Han wrote: > In Postgresql 7.3, a datatype can be int, text, etc, and also > pseudo-types like RECORD, any, etc. > > These pseudo types are mainly used in CREATE FUNCTIONs, but what if it's > used in a CREATE TABLE, esp. when the name of another table is used as a >

[GENERAL] CREATE TABLE with a column of type {table name}

In Postgresql 7.3, a datatype can be int, text, etc, and also pseudo-types like RECORD, any, etc. These pseudo types are mainly used in CREATE FUNCTIONs, but what if it's used in a CREATE TABLE, esp. when the name of another table is used as a datatype? e.g. -- Just for illustration: CREATE T

Re: [GENERAL] Don't removes/recycles WAL files at all

Tom Lane <[EMAIL PROTECTED]> writes: > Yeah, adding or removing -malign-double would change the layout of our > on-disk data structures, so it's no surprise you'd need to dump and > reload for that. > > Also, -ffast-math is known to be Evil. I thought we had a check to > prevent that (looks ...)

Re: [GENERAL] Port?

b b wrote: (B> (B> What port does the postgresql server listen on. (B (BIt listens on whichever port you tell it to :) 5432 by default I think. (B (B> How do we know the port postgresql is listening on? (B (BMake sure that tcp connections are enabled in the conf file. TCP (Bconnection a