Re: Re: How to keep at-most N rows per group? periodic DELETEs or constraints or..? - Mailing list pgsql-sql

From Jamie Tufnell
Subject Re: Re: How to keep at-most N rows per group? periodic DELETEs or constraints or..?
Date
Msg-id b0a4f3350801091530j56454688m27adfdb6eb28bc77@mail.gmail.com
Whole thread Raw
In response to Re: Re: How to keep at-most N rows per group? periodic DELETEs or constraints or..?  (Erik Jones <erik@myemma.com>)
List pgsql-sql
On 1/9/08, Erik Jones <erik@myemma.com> wrote:
> On Jan 9, 2008, at 1:09 PM, Scott Marlowe wrote:
> > On Jan 9, 2008 12:20 PM, Steve Midgley <public@misuse.org> wrote:
> >> This is kludgy but you would have some kind of random number test at
> >> the start of the trigger - if it evals true once per every ten
> >> calls to
> >> the trigger (say), you'd cut your delete statements execs by about
> >> 10x
> >> and still periodically truncate every set of user rows fairly
> >> often.
> >
> > And, if you always through a limit 50 on the end of queries that
> > retrieve data, you could let it grow quite a bit more than 60 or 70...
> > Say 200.  Then you could have it so that the random chopper function
> > only gets kicked off every 100th or so time.
>
> I like that idea.

I do too!  I'm going to have a shot at implementing this tomorrow.
Thanks for all your opinions guys :-)

Cheers,
Jamie


pgsql-sql by date:

Previous
From: Erik Jones
Date:
Subject: Re: Re: How to keep at-most N rows per group? periodic DELETEs or constraints or..?
Next
From: "Chinyi Woo"
Date:
Subject: Support for SQL TOP clause?