Re: [GENERAL] deleting records is failing

ge- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Glaesemann Sent: Wednesday, December 07, 2005 7:21 PM To: Tim Vadnais Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] deleting records is failing On Dec 8, 2005, at 12:13 , Tim Vadnais wrote: > I have a set

[GENERAL] deleting records is failing

This question is probably real easy to answer, but I've got myself into a vicious loop and can't see the forest through the trees. I have a set of records spanning several dates, and I want to delete some records within a specific date range. For example, I have a record for each day from Sept 1

Re: [GENERAL] Issue with adding ORDER BY to EXCEPT.

Perfect, Thanks so much to all who assisted me. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martijn van Oosterhout Sent: Tuesday, June 07, 2005 10:51 AM To: Scott Marlowe Cc: Jaime Casanova; Tim Vadnais; pgsql-general@postgresql.org; Hackers

[GENERAL] Issue with adding ORDER BY to EXCEPT.

Hi all, I've got myself into a vicious loop that I can't seem to get out of. I have paired down the query for debugging this particular problem that I'm having. What I'm trying to do is find all 'encounters' that have no matching record in 'p_l_d' for a date range. My first SELECT pulls all 'en

Re: [GENERAL] Update on tables when the row doesn't change

Hi All, Can someone please address this aspect of Sebastian's email? I, too, am interested in the response. >> Why does Postgres perform an update on the table even >> if no data changes? >> Can I circumvent this behaviour of Postgres? Tim -Original Message- From: [EMAIL PROTECTED] [m

[GENERAL] a SELECT FOR UPDATE question

Title: a SELECT FOR UPDATE question Hi, If I select a row for update, is there anyway that someone can query to see if that row has been 'selected for update' and by whom? Then I'd like to know if the session that 'SELECT(ed) FOR UPDATE' dies, will the server release the locked row? Than

[GENERAL] xlog flush request 0/215D32E4 is not satisfied

Title: xlog flush request 0/215D32E4 is not satisfied Can anyone help me with this problem; we are just about to go live (February 1), and all of a sudden our main database has an 'issue'.  I'd like to save the database if possible, if not, then I'll rebuild it from scratch which I absolutely

[GENERAL] VACUUM FULL [ANALYZE] problem

Title: VACUUM FULL [ANALYZE] problem If I run a vacuum full on my system I get the following warning.  The optional analyze  has no effect on the output. bwks=# VACUUM FULL; WARNING:  index "pg_database_datname_index" contains 3 row versions, but table contains 4 row versions HINT:  Rebuild

[GENERAL] field incrementing in a PL/pgSQL trigger

Title: field incrementing in a PL/pgSQL trigger Hi, My boss wants to add some logging functionality to some of our tables on update/delete/insert.  I need to log who, when, table_name, field name, original value and new value for each record, but only logging modified fields, and he wants m

[GENERAL] field incrementing in a PL/pgSQL trigger

const PGresult *, int); ) Using the dynamically generated name I could then walk the NEW and OLD columns to compare the values. (e.g. if (NEW.field != OLD.field) do something;); Can anyone help me with this? Thank you in advance. Tim Vadnais ---(end of broa

[GENERAL] field incrementing in a PL/pgSQL trigger

Hi, My boss wants to add some logging functionality to some of our tables on update/delete/insert. I need to log who, when, table_name, field name, original value and new value for each record, but only logging modified fields, and he wants me to do this wing postgres pgSQL triggers. We are give