| From: | chester c young <chestercyoung(at)yahoo(dot)com> |
|---|---|
| To: | Bryce Nesbitt <bryce1(at)obviously(dot)com> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Large journal as psql table. Good idea? Triggering. |
| Date: | 2007-04-24 00:56:19 |
| Message-ID: | 448237.8848.qm@web54314.mail.yahoo.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
> But I'm thinking that maybe it's a job for a database table. Each
> new
> row would be written with a status (10="new"). And that the modem
> process would poll for new rows. Problem is there will be lots of
> rows,
> but only a trivial few will be "new". The huge index file and the
> polling seem like a drag on the database, unless there is a way to
> optimize.
create index <name> on <table>( <id> ) where status = 'new';
this index will be very fast.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitry Turin | 2007-04-24 11:58:49 | Fwd: Re[2]: We all are looped on Internet: request + transport = invariant |
| Previous Message | Phillip Smith | 2007-04-23 23:27:03 | Large journal as psql table. Good idea? Triggering. |