Josh Berkus wrote:
Tim,
That loop apparently does not find any matching rows, which would
have been inserted just before this row was, inside the same
transaction.
It was successfully finding those rows before, when the trigger was
AFTER INSERT. If I manually select those rows after the query
Ludwig Lim wrote:
Try changing the "AFTER" to "BEFORE"
CREATE TRIGGER projtask_insert_depend_trig BEFORE...
Changes made to the "NEW" will not be reflect in the
AFTER trigger since, the row is already inserted.
Thanks, however this seems to present a different problem now.
FOR depe
I have created a function in pl/pgsql to modify a row before it gets put
into the database, but it seems my modification is being ignored, and
the unmodified row is being inserted.
I have confirmed with this RAISE EXCEPTION that my "NEW" row is modified
properly, however it is not being stored
Marie G. Tuite wrote:
Here is a function that I use to list fk(triggers) on a table. Execute the
function to get the trigger name and then - drop trigger "trigger_name" on
table_name;
Thanks for the function. Strangely enough, it appears the "extra"
triggers are gone all by themselves. It seem
I'm trying to comb through my database and add ON DELETE CASCADE to a
number of tables where I already have fkeys in place, but I'm having a
hard time.
ALTER TABLE project_task DROP CONSTRAINT
"project_task_group_project_id_f" RESTRICT;
ERROR: ALTER TABLE / DROP CONSTRAINT: project_task_group
I see there are a handful of reports of this, but it does seem broken to
me. If I am copying a table and a column is blank, surely it makes sense
to substitute the column default from the table? Right now, it is
substituting 0 for a null column, instead of -99 as I wished, and here I
was compla
Maurício Sessue Otta wrote:
Hi, in my production server a "du -hs" in the DATA directory
returns 21GB
in a newly installed server, after I restored the dumps from the
production server, the "du -hs" gives me just 8GB
why is there such a diference???
what should I do (besides buying bigger and b
On Fri, Oct 25, 2002 at 12:24:43PM -0400, Tom Lane wrote:
> If you skipped enable-locale then you are outta luck. The fact that
> there is a connection between "a" and "accented a" is purely a locale
> issue.
What I meant was, if I recompile --enable-locale and install over the current
builds, I
On Fri, Oct 25, 2002 at 10:37:59AM -0400, Tom Lane wrote:
> Tim Perdue <[EMAIL PROTECTED]> writes:
> > I compiled postgres with --enable-multibyte and --enable-recode, and it
> > doesn't appear to help with my problem.
>
> I think this is a locale issue,
1') from latlong where ccode='BR';
ERROR: Could not convert UTF-8 to ISO8859-1
Also, my "Up Arrow" and "Delete" keys no longer work since I recompiled 7.2.3
on debian.
Thanks for any help,
Tim Perdue
---(end of broadcast)---
On Thu, Sep 12, 2002 at 12:49:21PM -0500, Larry Rosenman wrote:
> Look at contrib/earthdistance, I **think** it does what you need.
Thanks, yeah this starts to get me into the realm of what I need. It still
has to run every possible permutation to figure out which one is closest for
each postalco
Hi Folks -
I'm working on a global weather database for a client and have hit an issue
which I'm sure has been solved before. Unfortunately, the site search doesn't
pull up anything.
Essentially, I've got two tables, one with city/county/lat/long and another
with lat/long/weather data.
None of
On Fri, Apr 13, 2001 at 11:11:26AM -0400, Tom Lane wrote:
> Tim Perdue <[EMAIL PROTECTED]> writes:
> > Does it still work with those revised CREATE statements?
>
> Yes, works fine here.
>
> >> What version are you using?
>
> > That's RC3 and RC
On Fri, Apr 13, 2001 at 03:02:32AM -0400, Tom Lane wrote:
> Tim Perdue <[EMAIL PROTECTED]> writes:
> > However, I keep getting this error, and I don't know what it means:
> > ERROR: FULL JOIN is only supported with mergejoinable join conditions
>
> Works for me
Looking at the docs for 7.1, it appears that full outer joins are supported:
http://www.postgresql.org/devel-corner/docs/user/queries.html
However, I keep getting this error, and I don't know what it means:
ERROR: FULL JOIN is only supported with mergejoinable join conditions
I've tried several
On Thu, Apr 05, 2001 at 10:46:07AM -0400, Tom Lane wrote:
> Tim Perdue <[EMAIL PROTECTED]> writes:
> > Our database is about 1GB in total size, the machine has 4GB, but the entire
> > system is only using 1.2 GB, even during vacuum or a daily, extremely large
> > q
I thought this was an interesting thread because we're running into
problems with IO under 7.1 during vacuum and a couple of scheduled aggregation
jobs.
Our database is about 1GB in total size, the machine has 4GB, but the entire
system is only using 1.2 GB, even during vacuum or a daily, extreme
We recently upgraded sourceforge to 7.1b6 from our nice old stable november
cvs snapshot and we hit this error last nite:
NOTICE: FlushRelationBuffers(groups, 2140): block 2057 is referenced (private
0, global 1)
Error: ERROR: VACUUM (repair_frag): FlushRelationBuffers returned -2
I tend to
Probably worth noting that this could be normalized into at least 3 tables
from what I can tell.
Tim
On Wed, Mar 14, 2001 at 11:03:01PM +, Oliver Elphick wrote:
> Srikanth Rao wrote:
> >Hi,
> >I have a table like this:
> > location| numbrochures | marketing
> >-
On Wed, Mar 14, 2001 at 01:09:18PM -0500, Tom Lane wrote:
> Tim Perdue <[EMAIL PROTECTED]> writes:
> > This is related to the plpgsql project I was working on this morning. I'm
> > trying to create a rule, so that when a row is inserted into a certain table,
> >
This is related to the plpgsql project I was working on this morning. I'm
trying to create a rule, so that when a row is inserted into a certain table,
we also create a row over in a "counter table". The problem lies in getting
the primary key value (from the sequence) so it can be inserted in tha
On Wed, Mar 14, 2001 at 10:33:49AM -0500, Bruce Momjian wrote:
> It is hard to test this without the table schema, but I think you are
> missing some END IF's in the code above. Those are not elif's, but
> actual new IF's that need their own END IF, I think.
Oh wow - this is almost like going ba
Hello all - I apologize for the newbie-esque question, but the debug output
from postgres when you have a bug in your PL/pgSQL procedure is none to
detailed.
I've created the following procedure and am getting an error when I try to
update the table. The error is something like "parse error near
23 matches
Mail list logo
