[ADMIN] trigger

2005-11-18 Thread Aftab Alam
Hello, I want to create a trigger in PostgresSQL In trigger, Before inserting the record, if data is already in the table, the trigger fire the mesaage that data is already there, and after that trigger ckeck for next insert statement. Pleae help me in this regard , kindly  reply. Regards

[ADMIN] Select waiting

2005-11-18 Thread Armel HERVE
Hello there, when I have connections waiting, can I kill the root connection which is the origin of the lock, without restarting the postgres server ? I know it's not a good practice, but we are in a development step... Thanks for your answers (and sorry for my poor English :-) ) Armel

[ADMIN] Version 8.1

2005-11-18 Thread Diego
Hi, I have this SQL working very well in 8.0: {SELECT *, tabpes.cod, tabpes.nome FROM fincli_pesaut WHERE TRUE AND id_cli = '001/12' AND id_pes = tabpes.id} Why don´t work in 8.1? ERROR: missing FROM-clause entry for table "tabpes" []s Diego Ziquinatti ---(end of br

Re: [ADMIN] Version 8.1

2005-11-18 Thread Peter Eisentraut
Diego wrote: > Why don´t work in 8.1? Because it is violating the SQL standard and 8.1 is stricter in that regard. > ERROR: missing FROM-clause entry for table "tabpes" So add that table to the FROM clause. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---

[ADMIN] Diffs between two databases...

2005-11-18 Thread Mario Splivalo
I have a production server (7.4.9) with, of course, a production database with 30 tables, 250 functions, types, views, indices, ... My developers have created new version of the software, that includes the new version of the datbase. They've changed 6 tables, two dozen views and almost one hundred

Re: [ADMIN] Diffs between two databases...

2005-11-18 Thread Alvaro Herrera
Mario Splivalo wrote: > I've seen that I can do pg_dump to a file with pg_dump -Fc, and then I > can do pg_restore -Fc -l to have the list of all the > database objects. There I can see the functions, but how do I (re)create > just the desired function? Use pg_restore -L. > What would suit me t

[ADMIN] Suggested HW for postgres ?

2005-11-18 Thread Enrico Weigelt
Hi folks, we're going to buy new hardware for an postgresql database server. High availability is important, so I'm thinking of an Athlon System w/ 2GB RAM and UW-SCSI RAID. But what hardware should I use ? And what RAID configuration would be the best ? cu --

Re: [ADMIN] Suggested HW for postgres ?

2005-11-18 Thread Scott Marlowe
On Fri, 2005-11-18 at 13:05, Enrico Weigelt wrote: > Hi folks, > > > we're going to buy new hardware for an postgresql database server. > High availability is important, so I'm thinking of an > Athlon System w/ 2GB RAM and UW-SCSI RAID. > > But what hardware should I use ? > And what RAID conf

[ADMIN] Server Hardware Configuration

2005-11-18 Thread Michael D. Sofka
We are running PostgreSQL as the back-end to a spam scanning system. The database holds suspected spam, and user configuration information. A web interface allows people to accept, or (usually) discard the trapped messages. So, most data is write once, read at most once, delete. The total siz

[ADMIN] COPY and partitioning

2005-11-18 Thread Colton A Smith
Hi I understand v8.1 implements table partitioning. Very exciting! I have a big table (30 G) that is a real headache. I'd like to partition it. My plan is the following: (1) use pg_dump -t to dump the data; (2) create a partitioning schema with check constraints; and (3) repopulate usin

[ADMIN] Select waiting

2005-11-18 Thread Armel HERVE
Hello there, when I have connections waiting, can I kill the root connection which is the origin of the lock, without restarting the postgres server ? I know it's not a good practice, but we are in a developpement step... Thanks for your answers (adn sorry for my poor english :-) ) -- Armel

[ADMIN] fsm allocation

2005-11-18 Thread Colton A Smith
Hi I manage a moderately large database (version 8.0.4) that experiences about 500 inserts per hour spread over a half dozen tables. Not many updates or deletions (usually). My problem involves fsm allocation and the vacuum utility. Recently, I vacuumed and the output told me I had 47

Re: [ADMIN] md5 collision generator

2005-11-18 Thread Wim Bertels
On Wed, 2005-11-16 at 18:31 +0100, Wim Bertels wrote: > On Wed, 2005-11-16 at 10:29 -0500, Tom Lane wrote: > > Wim Bertels <[EMAIL PROTECTED]> writes: > > > the sourcecode of a md5 collision generator has been released, > > > it takes about 45 minutes to generate. > > > ..so to an "eve" with this k

Re: [ADMIN] Suggested HW for postgres ?

2005-11-18 Thread Joel Stevenson
At 8:05 PM +0100 11/18/05, Enrico Weigelt wrote: Hi folks, we're going to buy new hardware for an postgresql database server. High availability is important, so I'm thinking of an Athlon System w/ 2GB RAM and UW-SCSI RAID. But what hardware should I use ? And what RAID configuration would be t

Re: [ADMIN] fsm allocation

2005-11-18 Thread Andrew Sullivan
On Thu, Nov 17, 2005 at 08:20:12AM -0500, Colton A Smith wrote: > By the way, what exactly is the 'free map space' anyway? And why does > it need so much space? There's a useful description in the docs, section 17.4.2 (for 8.1). I'd look at that. Your usage might not be stable right now becau

Re: [ADMIN] fsm allocation

2005-11-18 Thread Tom Lane
Colton A Smith <[EMAIL PROTECTED]> writes: >Recently, I vacuumed and the output told me I had 47 relations, 151751 > pages stored, and that I needed 237680 total pages. My fsm allocation > was for 1000 relations, 15 pages. >I took this to mean the vacuum didn't work and that I needed

Re: [ADMIN] COPY and partitioning

2005-11-18 Thread Guido Barosio
Thinking about dumping the schema, rewriting that structure with your partitioning needs, and after copy the data.   Why not?   Just 2 cents, never done it.   to dump a schema: pg_dump -s dbname > dbname.schema    Then just restore the data, it should work I guess.   Best regards, Guido  On 11/17/

Re: [ADMIN] Server Hardware Configuration

2005-11-18 Thread John Jensen
Performance questions are terrible to answer because we all use our systems in different ways. Here's my 2 bits for what they're worth. > The idea behind the first is to keep the > entire database in memory, by way of the disk cache. What you describe is a real-time system. Does your requireme