| From: | Jeff Frost <jeff(at)frostconsultingllc(dot)com> |
|---|---|
| To: | Dirk Jagdmann <jagdmann(at)gmail(dot)com> |
| Cc: | Daniel CAUNE <d(dot)caune(at)free(dot)fr>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: keeping last 30 entries of a log table |
| Date: | 2006-06-20 14:12:41 |
| Message-ID: | Pine.LNX.4.64.0606200711540.22565@discord.home.frostconsultingllc.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Tue, 20 Jun 2006, Dirk Jagdmann wrote:
>> Column id should be indexed indeed. Anyway, I'm not sure about any
>> performance improvement using that last method, as the most consuming
>> operation might be the DELETE operation, not really the SELECT operation,
>> when dealing with a huge volume of data.
>
> why worry, there are a maximum of 30 Entries in this table anyway. So
> even the most unoptimized select and delete combinations should be
> very fast...
Well, it's 30 entries per account and likely 1000s of accounts, but still that
would only be 30,000-90,000 entries, so shouldn't be too bad.
--
Jeff Frost, Owner <jeff(at)frostconsultingllc(dot)com>
Frost Consulting, LLC http://www.frostconsultingllc.com/
Phone: 650-780-7908 FAX: 650-649-1954
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Juliann Meyer | 2006-06-20 18:44:42 | unknown sqlstate code |
| Previous Message | Dirk Jagdmann | 2006-06-20 13:48:02 | Re: keeping last 30 entries of a log table |