Thank you for response.
On Tue, Sep 19, 2023 at 2:52 AM Michael Paquier wrote:
> On Mon, Sep 18, 2023 at 05:49:51PM +0300, Sergey Sergey wrote:
> > Hope this patch will be usefull/
>
> -uint64 fpLockBits;/* lock modes held for each fast-path
> slot */
> +uint8
On Mon, Sep 18, 2023 at 05:49:51PM +0300, Sergey Sergey wrote:
> Hope this patch will be usefull/
-uint64 fpLockBits;/* lock modes held for each fast-path slot
*/
+uint8fpLockBits[FP_LOCK_SLOTS_PER_BACKEND];/* lock modes
If my maths are right, this makes
Hope this patch will be usefull/
On Mon, Sep 18, 2023 at 5:47 PM Sergey Sergey wrote:
> While replaying our production workload we have found Postgres spending a
> lot of time inside TimescaleDB planner. The planner itself need an
> information about whether a table involved is a TimescaleDB
While replaying our production workload we have found Postgres spending a
lot of time inside TimescaleDB planner. The planner itself need an
information about whether a table involved is a TimescaleDB hypertable. So
planner need an access to TimescaleDB internal metainformation tables. This
