Thanks a lot Jeremy, we ended up integrating the code you provided
into our software (just before you patent it) :)
Best regards,
Kkh
On Tue, Oct 3, 2017 at 7:58 PM, Schneider wrote:
> On Mon, Oct 2, 2017 at 10:27 AM, Khalil Khamlichi
> wrote:
>> we have records like this
>>
Thanks, I'll check it out.
Sent via mobile, please forgive typos and brevity
On Oct 14, 2017 3:23 PM, "Joshua D. Drake" wrote:
> On 10/01/2017 01:17 AM, Khalil Khamlichi wrote:
>
>> Hi everyone,
>>
>
> Take a look at TimescaleDB they have an extension to
hat updates every minute with a trigger that updates
>> another table with information from the stream. That way I'm constantly
>> updated with no need to run a script to update before I want a report.
>>
>> Clifford
>>
>> On Sun, Oct 1, 2017 at 10:08 AM, Me
interesting proposition, I am reading the docs.
On Mon, Oct 2, 2017 at 6:08 PM, Scott Marlowe
wrote:
> On Sun, Oct 1, 2017 at 2:17 AM, Khalil Khamlichi
> wrote:
> > Hi everyone,
> >
> > I have a data stream of a call center application coming in to postg
Hi everyone,
I have a data stream of a call center application coming in to postgres in
this format :
user_name, user_status, event_time
'user1', 'ready', '2017-01-01 10:00:00'
'user1', 'talking', '2017-01-01 10:02:00'
'user1', 'after_call', '2017-01-01 10:07:00'
'user1', 'ready', '2017-01-01 1
You can keep using redis and use FDW to access it as if it was a postgres
table.
It does read and write to redis and can present redis data as regular
tables to you.
I never really had to choose between redis and postgres. Postgres was
always for safety and persistance and redis for sharing data an
