Search Postgresql Archives

Re: How to perform a long running dry run transaction without blocking

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: How to perform a long running dry run transaction without blocking
From: Rob Sargent <robjsargent@xxxxxxxxx>
Date: Thu, 6 Feb 2025 11:53:38 -0700
Cc: Adrian Klaver <adrian.klaver@xxxxxxxxxxx>, pgsql-general <pgsql-general@xxxxxxxxxxxxxx>
In-reply-to: <0FE9C709-A108-4ED5-8132-B802B8D9908F@princeton.edu>
References: <0FE9C709-A108-4ED5-8132-B802B8D9908F@princeton.edu>

> 
Have you considered a validation app? Have it read the inputs and look in db for conflicts, rather than attempt the insert. Zero transactions necessary

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: How to perform a long running dry run transaction without blocking
  - From: Robert Leach

References:
- Re: How to perform a long running dry run transaction without blocking
  - From: Robert Leach

Prev by Date: Re: libc to libicu via pg_dump/pg_restore?
Next by Date: Re: How to perform a long running dry run transaction without blocking
Previous by thread: Re: How to perform a long running dry run transaction without blocking
Next by thread: Re: How to perform a long running dry run transaction without blocking
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux