Re: [SQL] Large journal as psql table. Good idea? Triggering.

2007-04-23 Thread chester c young
> 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 > pollin

[SQL] Large journal as psql table. Good idea? Triggering.

2007-04-23 Thread Phillip Smith
If it's going to be too big for a database, then it's going to be worse using flat-files on a disk :) I'd suggest putting it in a database, and have 2 tables: 1) "New" messages to be sent 2) Archive messages That way the polling machine only has to wait for the database to scan th

[SQL] Large journal as psql table. Good idea? Triggering.

2007-04-23 Thread Bryce Nesbitt
Dear Postgres folks; I'm considering using a postgres table for something that could be done with a flat file. Is this a good idea? I have events on a machine "A", which need to be sent by an SMS/Cell Phone modem that's on a totally different machine "B". Potentially this is a job for a flat fi