It completely depends on a lot of factors of course, so these numbers are
meaningless.
It depends at the very least on:
* The hardware (CPU, disk type + disk connection)
* The size of the records read/written
* The presence of indices and constraints.
So, adding some other meaningless numbers to a
Hi,
We are trying to find maximum throughput in terms of transactions per
second (or simultaneous read+write SQL operations per second) for a use
case that does one ACID transaction (consisting of tens of reads and tens
of updates/ inserts) per incoming stream element on a high-volume
high-velocit
How about using pg_hint_plans?
Check it out if it helps your case.
Thanks and Regards,
Nikhil
On Thu, Mar 18, 2021, 15:07 Manish Lad wrote:
> Thank you for your response.
>
>
>
>
> On Thu, 18 Mar 2021, 14:46 Gaetano Mendola, wrote:
>
>> There is not such functionality, you can enable/disable
