Re: Processing new rows in staging table quickly...
Date: Wed, 17 Apr 2019 23:14:14 -0400
Message-ID: <CAJoeKmv2QkeqGfkdyr3V9b3DEf=vd5xWDctU7QORAH_S6WosNQ_at_mail.gmail.com>
FBI, and Postgres supports it too.
Igor Neyman
On Wed, Apr 17, 2019 at 7:33 PM <post.ethan_at_gmail.com> wrote:
> I have a staging table in which 99% of the rows are going to have a date
> for stats_processed_time.
>
>
>
> I will need to only select for rows that have not been processed.
>
>
>
> What is the best strategy here? Should I allow nulls and select like
> below? Or should I put a date, way out in the future, say 2099, and select
> for that instead and then update to correct data once things are processed?
> Perhaps allow nulls and a bitmap or FBI solution (I would like to avoid
> solutions which can’t be ported to Postgres.)
>
>
>
> …
>
> where b.access_key=v_access_key
>
> and b.bucket=v_bucket
>
> and b.stats_processed_time is null
>
-- http://www.freelists.org/webpage/oracle-lReceived on Thu Apr 18 2019 - 05:14:14 CEST