Re: [GENERAL] PostgreSQL 64 Bit XIDs - Transaction IDs

2012-03-24 Thread Scott Marlowe
On Fri, Mar 23, 2012 at 11:18 PM, Bret Stern bret_st...@machinemanagement.com wrote: VoltDB maybe - Original Message - VoltDB has a completely different focus than PostgreSQL really. PostgreSQL is a general purpose database that can achieve some very impressive numbers using super fast

Re: [GENERAL] PostgreSQL 64 Bit XIDs - Transaction IDs

2012-03-24 Thread Scott Marlowe
On Sat, Mar 24, 2012 at 1:27 AM, Scott Marlowe scott.marl...@gmail.com wrote: On Fri, Mar 23, 2012 at 11:18 PM, Bret Stern bret_st...@machinemanagement.com wrote: VoltDB maybe - Original Message - VoltDB has a completely different focus than PostgreSQL really. PostgreSQL is a

[GENERAL] group by does not show error

2012-03-24 Thread AI Rumman
I am using Postgresql 9.1.0. I found that following GROUP BY query works in my DB :- \d t1 Table public.t1 Column | Type | Modifiers +-+--- i | integer | not null nam| text| Indexes: t1_pkey PRIMARY KEY, btree (i) select i,nam from

Re: [GENERAL] group by does not show error

2012-03-24 Thread Thomas Kellerer
AI Rumman wrote on 24.03.2012 09:06: I am using Postgresql 9.1.0. I found that following GROUP BY query works in my DB :- \d t1 Table public.t1 Column | Type | Modifiers +-+--- i | integer | not null nam| text| Indexes: t1_pkey PRIMARY

Re: [GENERAL] broken xlog - recovery plan check

2012-03-24 Thread Thom Brown
On 24 March 2012 00:45, Colin Taylor colin.tay...@gmail.com wrote: Hi I seem to have an 8.3.9 database with a broken xlog, PANIC:  heap_insert_redo: invalid max offset number My plan is to run pg_resetxlog. Hopefully it then starts up. Test recent data as thoroughly as possible - (script

Re: [GENERAL] plpgsql function to insert or update problem

2012-03-24 Thread Alban Hertroys
On 23 Mar 2012, at 19:49, Andy Colson wrote: Anyway, the problem. I get a lot of DB Error messages: DB Error: ERROR: duplicate key value violates unique constraint by_ip_pk DETAIL: Key (ip, sessid, time)=(97.64.237.59, 2qggi9gcdkcaoecqg3arvo1gu7, 2012-03-23 13:00:00) already exists.

Re: [GENERAL] pgcon 2012

2012-03-24 Thread Bruce Momjian
On Sat, Mar 24, 2012 at 04:46:49AM +, Arvind Singh wrote: Dear sir, we are recent users of Postgres and wish to be more aware and soak up the activities around the DB. we used to develop more on MySql , SQl Server combo Now we are using PG 9.0.5 , NPGSQL + Visual CSharp , Java

Re: [GENERAL] plpgsql function to insert or update problem

2012-03-24 Thread Andy Colson
On 03/24/2012 05:23 AM, Alban Hertroys wrote: On 23 Mar 2012, at 19:49, Andy Colson wrote: Anyway, the problem. I get a lot of DB Error messages: DB Error: ERROR: duplicate key value violates unique constraint by_ip_pk DETAIL: Key (ip, sessid, time)=(97.64.237.59,

[GENERAL] Howto Replication for dummies?

2012-03-24 Thread Andreas
Hi, I've got a PG 9.1.3 on an OpenSuse 12.1 runnig that lately crashed because of memory allocation errors probaply due to failing RAMs. In this case the server died thursday afternoon and at first didn't comlain when I restartet it. Later some queries produced out of memory errors which is

Re: [GENERAL] Table growing faster than autovacuum can vacuum

2012-03-24 Thread Jasen Betts
On 2012-02-15, Asher Hoskins as...@piceur.com wrote: Hello. I've got a database with a very large table (currently holding 23.5 billion rows, the output of various data loggers over the course of my PhD so far). The table itself has a trivial structure (see below) and is partitioned by

Re: [GENERAL] Table growing faster than autovacuum can vacuum

2012-03-24 Thread Scott Marlowe
On Sat, Mar 24, 2012 at 9:40 PM, Jasen Betts ja...@xnet.co.nz wrote: have you tried using COPY instead of INSERT (you'll have to insert into the correct partition) triggers fire on copy, but rules do not. So if he has partitioning triggers they'll fire on the parent table etc. HOWEVER,

Re: [GENERAL] Upgrade questions

2012-03-24 Thread Jasen Betts
On 2012-03-12, Carson Gross carsongr...@gmail.com wrote: We've got a postgres database with *a lot* of data in one table. On the order of 100 million rows at this point. Postgres is, of course, handling it with aplomb. ALTER TABLE my_table ALTER COLUMN id TYPE bigint; However, given