AW: Question on postgres certified OS platforms

2020-10-15 Thread Dirk Krautschick
Hi Raj, I am not aware of any official platform compatibility matrix but the Best way to find out is the status pane of the build farm https://buildfarm.postgresql.org/cgi-bin/show_status.pl Here you can search for your requested OS and check the test results for the last 5 releases. Some detai

Re: Date Format 9999-12-31-00.00.00.000000

2020-10-15 Thread Kyotaro Horiguchi
At Thu, 15 Oct 2020 17:59:39 -0700, Adrian Klaver wrote in > On 10/15/20 1:58 PM, Dirk Krautschick wrote: > > Hi, > > because of a migration from DB2 we have a lot of timestamps like > > -12-31-00.00.00.00 > > I'm assuming these got stored in a varchar field? It seems like an (old-styl

Re: Date Format 9999-12-31-00.00.00.000000

2020-10-15 Thread Adrian Klaver
On 10/15/20 1:58 PM, Dirk Krautschick wrote: Hi, because of a migration from DB2 we have a lot of timestamps like -12-31-00.00.00.00 I'm assuming these got stored in a varchar field? What would be the best way to handle this in Postgres also related to overhead and performance (ind

Re: UUID with variable length

2020-10-15 Thread Christophe Pettus
> On Oct 15, 2020, at 13:49, Dirk Krautschick > wrote: > Or do you have some other ideas how to use a primary key datatype like UUID > but with variable length? You're probably best off storing it as a VARCHAR() with a check constraint or constraint trigger that validates it. -- -- Christo

Question on postgres certified OS platforms

2020-10-15 Thread Raj Iyer
Hi, Is there information available on what versions of Postgres are certified and supported on what Operating System platforms. Thanks, Raj Confidentiality Notice: Amwell is a registered trademark of American Well Corporation. This email is the property of American Well, Inc This e-mail messag

Date Format 9999-12-31-00.00.00.000000

2020-10-15 Thread Dirk Krautschick
Hi, because of a migration from DB2 we have a lot of timestamps like -12-31-00.00.00.00 What would be the best way to handle this in Postgres also related to overhead and performance (index usage?). Or is TO_TIMESTAMP('-12-31-00.00.00.00', '-MM-DD-HH24.MI.SS.US') the only

UUID with variable length

2020-10-15 Thread Dirk Krautschick
Hi, I have here a situation with the usage of UUID. Here the database user allows UUIDs with less then 16 byte lengths (please don't ask :-) ). Of course there are some technical ways to do the filling of the not used bytes but I hope there is a better solution. This UUID is used as primary Key

Re: character datatype explaination sought

2020-10-15 Thread Adrian Klaver
On 10/15/20 7:07 AM, James B. Byrne wrote: I am testing Idempiere and have run across this in an example: character(1) DEFAULT 'Y'::bpchar NOT NULL, How does this differ from character(1) DEFAULT 'Y' NOT NULL, It doesn't. From here: https://www.postgresql.org/docs/current/typeconv-query.htm

Re: character datatype explaination sought

2020-10-15 Thread Tom Lane
"James B. Byrne" writes: > I am testing Idempiere and have run across this in an example: > character(1) DEFAULT 'Y'::bpchar NOT NULL, > How does this differ from > character(1) DEFAULT 'Y' NOT NULL, It doesn't. The former is just written with an explicit cast, which the latter lacks, but the

Re: character datatype explaination sought

2020-10-15 Thread Laurenz Albe
On Thu, 2020-10-15 at 10:07 -0400, James B. Byrne wrote: > I am testing Idempiere and have run across this in an example: > > character(1) DEFAULT 'Y'::bpchar NOT NULL, > > How does this differ from > > character(1) DEFAULT 'Y' NOT NULL, It is the same, only in the first version the type cast i

character datatype explaination sought

2020-10-15 Thread James B. Byrne
I am testing Idempiere and have run across this in an example: character(1) DEFAULT 'Y'::bpchar NOT NULL, How does this differ from character(1) DEFAULT 'Y' NOT NULL, -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Unencrypted

Re: Need to trace the logs

2020-10-15 Thread Pavel Stehule
čt 15. 10. 2020 v 15:51 odesílatel hubert depesz lubaczewski < dep...@depesz.com> napsal: > On Thu, Oct 15, 2020 at 05:25:11PM +0530, nandha kumar wrote: > > Hi Team, > > We are using a postgresql database with 9.6.1 version, any way to > > trace the last modified object, procedure in Postgre

Re: Need to trace the logs

2020-10-15 Thread hubert depesz lubaczewski
On Thu, Oct 15, 2020 at 05:25:11PM +0530, nandha kumar wrote: > Hi Team, > We are using a postgresql database with 9.6.1 version, any way to > trace the last modified object, procedure in PostgreSQL. well, you can log all queries, and extract the info from logs. If by "object" you mean table

Need to trace the logs

2020-10-15 Thread nandha kumar
Hi Team, We are using a postgresql database with 9.6.1 version, any way to trace the last modified object, procedure in PostgreSQL. Regards, Nandhakumar B

Re: rum index supported on pg13?

2020-10-15 Thread Teodor Sigaev
Done, thank you On 14.10.2020 19:30, Devrim Gündüz wrote: Hi Teodor, On Wed, 2020-10-14 at 18:49 +0300, Teodor Sigaev wrote: Thank you, fixed and published. Can you please release a new tarball? We need that to build the RPM packages. I'm still seeing 1.3.6 as the latest version. Thanks!

Re: Failed to compile libpq

2020-10-15 Thread Igor Korot
Tom, On Thu, Oct 15, 2020 at 12:16 AM Tom Lane wrote: > > Igor Korot writes: > > On Thu, Oct 15, 2020 at 12:01 AM Tom Lane wrote: > >> Kinda looks like you're using some non-GNU make. > > > Correct. > > It is from Solaris Studio compiler. > > > What should I do? > > Try "gmake". If it's not al