Re: Support for dates before 4713 BC

On Mon, 22 Aug 2022 at 11:14, stefan eichert wrote: > I can also fully support what Alex has written. I am an archaeologist at the > Natural History Museum Vienna and PostgreSQL is a perfect Open Source > software and we really love working with it for our archaeological and > (pre)historical

Db log error

Hello sir, I am getting log error like below FATAL: unsupported frientend protocol 1234.5680: server supports 1.0 to 3.0 I am using PostgreSQL 9.6.3 version and redhat 7.3 version efm 4.1 version. Above error is repeated in db log file how to identify the issue and how to fix. Please could sug

Re: Support for dates before 4713 BC

On 2022-08-23 10:25:12 +0100, Simon Riggs wrote: > On Mon, 22 Aug 2022 at 11:14, stefan eichert wrote: > > In order to deal with all dates, historical and prehistoric ones, in > > a consistent way, the implementation of timestamps/dates for before > > 4713 BC would be very helpful, as we really do

Re: Db log error

eswar reddy writes: > FATAL: unsupported frientend protocol 1234.5680: server supports 1.0 to 3.0 This is from a client library trying to use GSSAPI encryption, which that old server doesn't understand. You could ignore these messages, or you could update to a Postgres version that's not EOL.

Re: Support for dates before 4713 BC

> On 23/08/2022 14:38 CEST Peter J. Holzer wrote: > > > On 2022-08-23 10:25:12 +0100, Simon Riggs wrote: > > On Mon, 22 Aug 2022 at 11:14, stefan eichert > > wrote: > > > In order to deal with all dates, historical and prehistoric ones, in > > > a consistent way, the implementation of times

RE: Unable to start replica after failover

We know what the problem is, but don't know how to solve it correctly. After failover, *new leader* promoted and read local partial log to LSN 54E/FB348118 -> 2022-05-23 01:47:52.124 [12088] LOG: record with incorrect prev-link 0/100 at 54E/FB348118 2022-05-23 01:47:52.124 [12088] LOG: redo don

Possible values of DATESTYLE / PGDATESTYLE

Hi! I can find possible values for the DATESTYLE parameter in an old 7.2 doc page: https://www.postgresql.org/docs/7.2/sql-set.html But when switching to V14 there are no more values listed in the equivalent page... Where can I find the list of possible values for this DATESTYLE parameter, for

Re: Possible values of DATESTYLE / PGDATESTYLE

## Sebastien Flaesch (sebastien.flae...@4js.com): > Where can I find the list of possible values for this DATESTYLE parameter, > for V14? https://www.postgresql.org/docs/14/runtime-config-client.html#GUC-DATESTYLE Regards, Christoph -- Spare Space

Re: Possible values of DATESTYLE / PGDATESTYLE

Sebastien Flaesch writes: > I can find possible values for the DATESTYLE parameter in an old 7.2 doc page: > https://www.postgresql.org/docs/7.2/sql-set.html > But when switching to V14 there are no more values listed in the equivalent > page... All such info got moved to the per-setting documen

Corrupted Postgresql Microsoft Binaries

Hello, I downloaded the microsoft postgresql binaries for versions 14.5, 13.8, 12.12, 11.17, 10.22 from https://www.enterprisedb.com/download-postgresql-binaries and found that there was an error with opening the zip files. Does anyone else use these files and found that they ran into the same iss

Re: Corrupted Postgresql Microsoft Binaries

On 8/23/22 11:58, Hillary Masha wrote: Hello, I downloaded the microsoft postgresql binaries for versions 14.5, 13.8, 12.12, 11.17, 10.22 from https://www.enterprisedb.com/download-postgresql-binaries and found that there was an err

Re: Setting up a server with previous day data

Greetings, * Srinivasa T N (seen...@gmail.com) wrote: >I have a primary postgresql 12 server which is being continuously used > for transaction processing. For reporting purposes, I want to set up a > secondary server which has got previous day data. Everyday night, I want > the data from pr

Question regarding failover behavior

Hello all, I have a system that was originally set up on 9.3, a few years ago moved to 11.2 A shared mount is used to host the basebackup and wal archives. The failover procedure was basically manual and as follow: 1/ Take out the primary, remove the IP from the primary machine/VM 2/ Create the

Re: Surprising results from current_role in a "security invoker" trigger function in a "cascade delete via FK" scenario

> b...@yugabyte.com wrote: > >> david.g.johns...@gmail.com wrote: >> >> You are correct that the behavior here is not explicitly documented [where] >> I would expect to find it. >> >> My expectation is that the trigger owner is the context in which the trigger >> function is executed. Table ow

Re: Setting up a server with previous day data

On 7/19/22 02:22, Srinivasa T N wrote: Hi All,    I have a primary postgresql 12 server which is being continuously used for transaction processing.  For reporting purposes, I want to set up a secondary server which has got previous day data.  Everyday night, I want the data from primary to be

Re: Surprising results from current_role in a "security invoker" trigger function in a "cascade delete via FK" scenario

On Tue, Aug 23, 2022 at 5:12 PM Bryn Llewellyn wrote: > *What do you all think?* > > That bug reports should be sent to the -bugs mailing list with a succinct test case demonstrating the bug. David J.

Re: Surprising results from current_role in a "security invoker" trigger function in a "cascade delete via FK" scenario

david.g.johns...@gmail.com wrote:b...@yugabyte.com wrote:What do you all think?That bug reports should be sent to the -bugs mailing list with a succinct test case demonstrating the bug.I explained that the bug doesn't allow a short testcase because there are many degrees of freedom and you don't kn

Re: Surprising results from current_role in a "security invoker" trigger function in a "cascade delete via FK" scenario

On Tue, Aug 23, 2022 at 7:32 PM Bryn Llewellyn wrote: > > The account of my GitHub issue includes a preliminary test that shows that > there's something to investigate further. I copied it below. Please tell me > if it meets your succinctness criteria. If it does, then I'll submit it to > the psq

Re: recovery_command has precedence over phisical slots?

At Fri, 19 Aug 2022 18:37:53 +0200, Laurenz Albe wrote in > On Fri, 2022-08-19 at 16:54 +0200, Giovanni Biscontini wrote: > > Hello everyone,  > > I'm experiencing a behaviour I don't really understand if is a > > misconfiguration or a wanted behaviour: > > 1) I set up a primary server (a.k.a.

Re: Unable to start replica after failover

Hi, On Tue, 23 Aug 2022 at 16:31, Lahnov, Igor wrote: > > Our 'restore_command' on *previous leader* restores a partial file from > archive (from *new leader*) > > -> > 2022-05-23 01:50:14 [123730]: [1-1]: INFO: pg_probackup archive-get WAL > file: 0002054E00FB, remote: ssh, threads:

Re: Setting up a server with previous day data

On 2022-08-23 19:15:58 -0500, Ron wrote: > That was before someone developed a utility to convert the roll-forward logs > into INSERT, UPDATE and DELETE statements. > > Such a utility for PostgreSQL that would convert yesterday's WAL files into > SQL > would really solve your problem. Isn't that