From: | github kran <githubkran(at)gmail(dot)com> |
---|---|
To: | Mark Fletcher <markf(at)corp(dot)groups(dot)io> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Pulling data from Postgres DB table for every 5 seconds. |
Date: | 2019-01-09 18:10:09 |
Message-ID: | CACaZr5S8PKauzFFE2g5L4Kc4k7kY+bANBJfq1qXjEwPws2-dgw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Mark - We are currently on 9.6 version of postgres and cant use this
feature of logical replication.Answering to your question we are looking
for any changes in the data related to a specific table ( changes like any
update on a timestamp field
OR any new inserts happened in the last 5 seconds for a specific product
entity).
Any other alternatives ?.
On Wed, Jan 9, 2019 at 11:24 AM Mark Fletcher <markf(at)corp(dot)groups(dot)io> wrote:
> On Wed, Jan 9, 2019 at 9:02 AM github kran <githubkran(at)gmail(dot)com> wrote:
>
>>
>>> Hi Postgres Team,
>>>
>>> I have an application using RDS Aurora Postgresql 9.6 version having 4
>>> TB of DB size. In this DB we have a table PRODUCT_INFO with around 1
>>> million rows and table size of 1 GB.
>>> We are looking for a implementation where we want to pull the data in
>>> real time for every 5 seconds from the DB ( Table mentioned above) and send
>>> it to IOT topic whenever an event occurs for a product. ( event is any new
>>> product information or change in the existing
>>> product information.).
>>>
>>>
> It's unclear whether you want to do table scans or if you're just looking
> for changes to the database. If you're looking just for changes, consider
> implementing something using logical replication. We have a logical
> replication system set up to stream changes from the database into an
> elastic search cluster, and it works great.
>
> Mark
>
From | Date | Subject | |
---|---|---|---|
Next Message | github kran | 2019-01-09 18:11:47 | Re: Pulling data from Postgres DB table for every 5 seconds. |
Previous Message | Scot Kreienkamp | 2019-01-09 18:02:06 | RE: postgres operational |