Re: questions about wraparound

On Sat, 2021-04-03 at 15:22 +0200, Luca Ferrari wrote: > why having a TransactionId that is 32 bits > in depth while it is exposed (thru txid_current()) as a 64 bits value? > I mean, having 64 bits would reduce the need for anti-wrap arpund > vacuum. I suspect the usage of 32 bits is both for compa

LDAP, single sign on from Windows client

Hi I have a Linux server which is setup with authentication via LDAP against a Windows A/D. In pg_hba I have host ... ldap ldapserver=example.org ldapprefix="" ldapsuffix="@example.org" The user is also created in PostgreSQL but without a password. I can then login with psql from a Windows client

Re: MultiXactId wraparound and last aggressive vacuum time

After a closer reading of the documentation, it appears the database should stop accepting new transactions before a wraparound would ever occur. If so, then the only possible explanations for this multixactid wraparound error would be data corruption, or a bug in postgresql. The exact version I'

Upgrade from 11.3 to 13.1 failed with out of memory

Open Hi, I have aproximetly 560GB large database and try to upgrade it from 11.3 to 13.1. I’ve successfully upgraded dev,test and ref environment but on the production pg_dump failed with out of memory. Yes, of course, the dev,test and ref are much much smaller then production database. We are

Re: Upgrade from 11.3 to 13.1 failed with out of memory

On Tue, Apr 6, 2021 at 3:08 PM Mihalidesová Jana wrote: > > Open > > > Hi, > > > > I have aproximetly 560GB large database and try to upgrade it from 11.3 to > 13.1. I’ve successfully upgraded dev,test and ref environment but on the > production pg_dump failed with out of memory. Yes, of course,

RE: Open source licenses

My concern is, I guess, the same for all the software editor using opensource components. It is to make an inventory of all the used opensource licenses from all the used components, to check and respect the terms of use, to preserve copyrights and intellectual property. Companies providing o

Re: Open source licenses

On Tue, 2021-04-06 at 13:47 +, DAVID Nicolas wrote: > My concern is, I guess, the same for all the software editor using opensource > components. > > It is to make an inventory of all the used opensource licenses from all the > used components, > to check and respect the terms of use, to p

Re: questions about wraparound

On Tue, 06 Apr 2021 10:46:08 +0200 Laurenz Albe wrote: > On Sat, 2021-04-03 at 15:22 +0200, Luca Ferrari wrote: > > why having a TransactionId that is 32 bits > > in depth while it is exposed (thru txid_current()) as a 64 bits value? > > I mean, having 64 bits would reduce the need for anti-wrap

Re: LDAP, single sign on from Windows client

Greetings, * chlor (hans.sc...@gmail.com) wrote: > I have a Linux server which is setup with authentication via LDAP against a > Windows A/D. In pg_hba I have > host ... ldap ldapserver=example.org ldapprefix="" ldapsuffix="@example.org" > > The user is also created in PostgreSQL but without a pa

Re: MultiXactId wraparound and last aggressive vacuum time

On Mon, 5 Apr 2021 17:28:06 -0400 Michael Schanne wrote: > After a closer reading of the documentation, it appears the database should > stop accepting new transactions before a wraparound would ever occur. If > so, then the only possible explanations for this multixactid wraparound > error woul

Check constraint failure messages

I've got a domain that validates email addresses. When inserting a bunch of entries I simply get the error message ERROR: value for domain po.email violates check constraint "email_check" SQL state: 23514 When inserting 1000+ entries in a batch, finding the exact entry with the problem is notice

Re: Check constraint failure messages

On 4/6/21 2:40 PM, Miles Elam wrote: I've got a domain that validates email addresses. When inserting a bunch of entries I simply get the error message ERROR: value for domain po.email violates check constraint "email_check" SQL state: 23514 When inserting 1000+ entries in a batch, fi

Re: Check constraint failure messages

On Tue, Apr 6, 2021 at 1:03 PM Ron wrote: > On 4/6/21 2:40 PM, Miles Elam wrote: > > I've got a domain that validates email addresses. When inserting a bunch > of entries I simply get the error message > > ERROR: value for domain po.email violates check constraint "email_check" > SQL state: 23514

Re: Check constraint failure messages

On 4/6/21 3:50 PM, Miles Elam wrote: On Tue, Apr 6, 2021 at 1:03 PM Ron > wrote: On 4/6/21 2:40 PM, Miles Elam wrote: I've got a domain that validates email addresses. When inserting a bunch of entries I simply get the error message ERROR: va

Re: Check constraint failure messages

On Tue, Apr 6, 2021 at 1:59 PM Ron wrote: > > The blunt force answer is to not use bulk inserts. Try COPY; it's good at > saying which record throws an error. > Sadly, this is a cloud-managed database without direct access to 5432 from outside the VPC and bastian instances are frowned upon by o