From: | Garym <garym(at)oedata(dot)com> |
---|---|
To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Is there a cache consistent interface to tables ? |
Date: | 2018-02-09 07:56:00 |
Message-ID: | 18D16D27-E376-4ABE-888F-768BB674D0BF@oedata.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
This is an odd request for help. I'm looking to expose an interface so an external app can insert to a table while maintaining cache consistency and inserts be promoted via wal.
I need to support about 100k+ inserts/sec from a sensor data stream. It simply won't work using sql queries. If the call overhead is too high for single calls, multiple records per call is better. The data must be available for selects in 500ms. I current only have 24gb ram for pg, but production will be 56gb.
I'm taking this approach because pgpool2 chokes, delaying past requirements. I initially wanted to use wal, but masters don't want wal in feeds and slaves have unpredictable delays of seconds before provisioning occurs.
Suggestions are appreciated.
Gary
Sent from my iPad
From | Date | Subject | |
---|---|---|---|
Next Message | Konstantin Knizhnik | 2018-02-09 08:02:43 | Re: Using scalar function as set-returning: bug or feature? |
Previous Message | Sergei Kornilov | 2018-02-09 07:47:41 | Re: Using scalar function as set-returning: bug or feature? |