Re: Is there an equivalent to sp_getapplock, sp_releaseapplock in PostgreSql?

Hi Ityas Advisory locks do not act like the locks in MSSQL, Postgresql will ignore advisory locks for other transactions, its up the applications layer to poll/ obey/ enforce advisory locks You can do the type of locking as in MSSQL with Postgresql but its avoided in practice as that is the po

Re: Is there an equivalent to sp_getapplock, sp_releaseapplock in PostgreSql?

I’m not sure what these function exactly do in MSSQL but what in Postgres you probably can use “Advisory Locks” (https://www.postgresql.org/docs/9.4/explicit-locking.html ) in order to achive this. > On 13. Dec 2019, at 13:31, İlyas De

Is there an equivalent to sp_getapplock, sp_releaseapplock in PostgreSql?

In MSSQL I am using sp_getapplock, sp_releaseapplock. How can I achieve the same functionality in PostgreSql?

Re: Tuple concurrency issue in large objects

Shalini wrote: > > Is there a workaround to this concurrency issue without creating a > > new large object? The transaction failing with the "Tuple concurrently updated" error could be resubmitted by the client, as if it was a serialization failure. Or the failure could be preve

Re: How to Change collate & ctype for an existing database?

Hi pá 13. 12. 2019 v 9:57 odesílatel Daulat Ram napsal: > Hi, > > How we can change the Collate & Ctype from “c” to “C.UTF-8” on > existing production database. > > SELECT datcollate FROM pg_database WHERE datname='wwkidbt'; > > datcollate > > > > C > > postgres=# select versio

How to Change collate & ctype for an existing database?

Hi, How we can change the Collate & Ctype from "c" to "C.UTF-8" on existing production database. SELECT datcollate FROM pg_database WHERE datname='wwkidbt'; datcollate C postgres=# select version(); version ---