Turning fsync = off has resulted in no noticable build time reduction for
my Dockerfile with OSM Europe data, but still thank you for the suggestion!
>
On 3/30/24 03:14, Bandi, Venkataramana - Dell Team wrote:
Hi,
Clarifying the problem statement again, Multiple requests are getting to our
application server and using hibernate framework to persist the data into
Postgres SQL DB but for one of the request, it is also similar request like
On 3/29/24 17:16, David Gauthier wrote:
I tried encapsulating the DB name in double quotes (no good), single
quotes (still no good) escaping with '\' (no good), escaping with ".."
(no good).
SELECT * FROM "thedb.v1".theschem.thetab;
Just as documented.
On Sat, Mar 30, 2024 at 9:15 AM 黄宁 wrote:
> I want to develop a postgresql paid extension, then there is a local
> license file, how do I check if the license file is expired, check it once
> at each api execution, will that affect the performance of the api, is
> there any other way?
>
What
Hi,
Clarifying the problem statement again, Multiple requests are getting to our
application server and using hibernate framework to persist the data into
Postgres SQL DB but for one of the request, it is also similar request like
other requests and there are no differences b/w these requests
I want to develop a postgresql paid extension, then there is a local
license file, how do I check if the license file is expired, check it once
at each api execution, will that affect the performance of the api, is
there any other way?
That log snippet shows two different PIDs. Check the logs to see the
complete path that process 1876 took after it did the insert at 2024-02-19
15:21:54.850 +08
Make sure you are not using prepared transactions. This should return 0:
select current_setting('max_prepared_transactions');
Cheers,
Thank you, Justin -
On Sat, Mar 30, 2024 at 4:33 AM Justin Clift wrote:
> On 2024-03-30 05:53, Alexander Farber wrote:
> > I use the following postgresql.conf in my Dockerfile
> > ( the full version at https://stackoverflow.com/a/78243530/165071 ),
> > when loading a 28 GByte large
