pg_stat_reset round 3 - Mailing list pgsql-patches

From Christopher Kings-Lynne
Subject pg_stat_reset round 3
Date
Msg-id GNELIHDDFBOCMGBFGEFOGEIDCDAA.chriskl@familyhealth.com.au
Whole thread Raw
In response to Re: pg_stat_reset round 2  ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>)
Responses Re: pg_stat_reset round 3
Re: pg_stat_reset round 3
Re: pg_stat_reset round 3
List pgsql-patches
OK, I've attached a new patch where the function is marked volatile.  I
tested and you cannot have the function returning void, so I left it
returning boolean.

Chris

> -----Original Message-----
> From: pgsql-patches-owner@postgresql.org
> [mailto:pgsql-patches-owner@postgresql.org]On Behalf Of Christopher
> Kings-Lynne
> Sent: Monday, 5 August 2002 4:00 PM
> To: Neil Conway
> Cc: Patches
> Subject: Re: [PATCHES] pg_stat_reset round 2
>
>
> > It should be marked volatile (rather than stable), as it has
> > side-effects.
>
> OK, I'll fix it.
>
> > Wouldn't PG_RETURN_VOID() be more appropriate than returning true?
>
> I was under the impression that functions used in SELECTs cannot use
> PG_RETURN_VOID()...
>
> Chris
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>

Attachment

pgsql-patches by date:

Previous
From: "Christopher Kings-Lynne"
Date:
Subject: Re: pg_stat_reset round 2
Next
From: Tom Lane
Date:
Subject: Re: anonymous composite types for Table Functions (aka SRFs)