connects - Search results

Mailing lists  >>  pgsql-general  >>  Thread

2025-05-05 16:36:30 | Re: Different execution plans in PG17 and pgBouncer... (SERHAD ERDEM)

connected directly to the database we get a result in cca. 20 seconds. The same

Mailing lists  >>  pgsql-general  >>  Thread

2025-05-05 16:09:51 | Re: Different execution plans in PG17 and pgBouncer... (Efrain J. Berdecia)

connected directly to the database we get a result in cca. 20 seconds. The same

Mailing lists  >>  pgsql-general  >>  Thread

2025-05-05 16:07:24 | Re: Different execution plans in PG17 and pgBouncer... (SERHAD ERDEM)

connected directly to the database we get a result in cca. 20 seconds. The same

Mailing lists  >>  pgsql-general  >>  Thread

2025-05-05 15:51:20 | Re: Different execution plans in PG17 and pgBouncer... (Mladen Marinović)

connect_query parameter is not used. I can provide redacted explains if it would help

Mailing lists  >>  pgsql-general  >>  Thread

2025-05-05 15:38:51 | Re: Different execution plans in PG17 and pgBouncer... (SERHAD ERDEM)

connected directly to the database we get a result in cca. 20 seconds. The same

Mailing lists  >>  pgsql-general  >>  Thread

2025-05-05 15:36:24 | Re: Different execution plans in PG17 and pgBouncer... (Achilleas Mantzios)

connect_query inside pgbouncer's conf ? you have to show all configuration involved and also

Mailing lists  >>  pgsql-general  >>  Thread

2025-05-05 11:52:54 | Different execution plans in PG17 and pgBouncer... (Mladen Marinović)

connected directly to the database we get a result in cca. 20 seconds. The same