Re: pg_stat_reset() weirdness

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Joe Conway" <mail(at)joeconway(dot)com>
Cc: "Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_stat_reset() weirdness
Date: 2002-08-10 09:52:47
Message-ID: 00b401c24053$aed5b6e0$0200a8c0@SOL
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Ah doh - I thought it was catching it returning a boolean. I'll fix and
resubmit.

Chris

----- Original Message -----
From: "Joe Conway" <mail(at)joeconway(dot)com>
To: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
Cc: "Hackers" <pgsql-hackers(at)postgresql(dot)org>
Sent: Friday, August 09, 2002 11:26 PM
Subject: Re: [HACKERS] pg_stat_reset() weirdness

> Christopher Kings-Lynne wrote:
> > Hi guys,
> >
> > If you apply the pg_stat_reset() function patch you get this regression
> > failure. Is this because it's returning a bool I guess? Shall I just
fix
> > the regression test to exclude this function?
>
>
> > AND p1.proname != 'update_pg_pwd_and_pg_group';
> > oid | proname
> > ! ------+---------------
> > ! 2249 | pg_stat_reset
> > ! (1 row)
>
> Likely because this is now in CVS:
>
> DATA(insert OID = 2249 ( record PGNSP PGUID 4 t p t \054 0 0
> oidin oidout i p f 0 -1 0 _null_ _null_ ));
> #define RECORDOID 2249
>
> The Oids conflict.
>
> Joe
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2002-08-10 09:58:17 Re: Proposal: stand-alone composite types
Previous Message Christopher Kings-Lynne 2002-08-10 09:50:39 Re: pg_stat_reset() weirdness