On 8/3/22 18:13, Ron wrote:
On 8/3/22 20:02, Adrian Klaver wrote:
On 8/3/22 17:30, Ron wrote:
AWS RDS Postgresql 12.10
And https://www.postgresql.org/docs/12/sql-set-constraints.html seems to
say that SET CONSTRAINTS can make DEFERRABLE FKs temporarily not
deferrable.
What's the point?
On 2022-08-03 21:37, Rejo Oommen wrote:
Thank you for the reply Thomas. I agree with you on the mutual TLS
that you mentioned.
Here is what I was looking at.
The configurations at the server end will be with auth-method as md5
and auth-option as clientcert=verify-ca.
There's your issue. I
Hi,
On Wed, Aug 03, 2022 at 07:30:31PM -0500, Ron wrote:
>
> [quote]
> |DEFERRABLE|
> |NOT DEFERRABLE|
>
>This controls whether the constraint can be deferred. A constraint that
>is not deferrable will be checked immediately after every command.
>*Checking of constraints that are defer
On 8/3/22 20:02, Adrian Klaver wrote:
On 8/3/22 17:30, Ron wrote:
AWS RDS Postgresql 12.10
https://www.postgresql.org/docs/12/sql-createtable.html
[quote]
|DEFERRABLE|
|NOT DEFERRABLE|
This controls whether the constraint can be deferred. A constraint
that is not deferrable will be ch
On 8/3/22 17:30, Ron wrote:
AWS RDS Postgresql 12.10
https://www.postgresql.org/docs/12/sql-createtable.html
[quote]
|DEFERRABLE|
|NOT DEFERRABLE|
This controls whether the constraint can be deferred. A constraint
that is not deferrable will be checked immediately after every
comma
AWS RDS Postgresql 12.10
https://www.postgresql.org/docs/12/sql-createtable.html
[quote]
|DEFERRABLE|
|NOT DEFERRABLE|
This controls whether the constraint can be deferred. A constraint that
is not deferrable will be checked immediately after every command.
*Checking of constraints tha
=?UTF-8?B?QWxlxaEgWmVsZW7DvQ==?= writes:
> CREATE OR REPLACE FUNCTION tescase (_id_data_provider integer, _external_id
> bigint DEFAULT NULL::bigint, _external_complete_id character varying
> DEFAULT NULL::character varying)
> RETURNS TABLE(id_gm bigint, id_opp bigint, id_opp_state integer)
> LA
Hello,
I did some testing and the result is that on pg12 there are no such
problems. Pg13 and Pg 14.3 tests will follow but based on monitoring
processed RssAnon memory, I've found a correlation that only processes by a
single user are suffering from the memory allocation (it looks to be a
memory
On 2022-08-01 04:12, Rejo Oommen wrote:
Requirement is to use only ca.crt and connect to postgres
Server.crt, Server.key and ca.crt are configured at the postgres
server for tls connection.
Connection successful while using
psql ‘host=172.29.21.222 dbname=test user=postgres sslmode=verify-ca
I am pretty sure it was a free version of the install, however, I will check
the version tomorrow when I am back in the office.Thanks!Sent from my Verizon,
Samsung Galaxy smartphone
Original message From: Adrian Klaver
Date: 8/3/22 2:51 PM (GMT-05:00) To: zaphod61
, pgsql-ge
On 8/3/22 11:44, zaphod61 wrote:
The server version is 2016. The installer is the one listed on the
postgresql support page. I think version 12.3 was installed the same
way but that was before I came into contact with this application
Would be helpful to do:
select version();
to get some
On 8/3/22 11:44 AM, zaphod61 wrote:
The server version is 2016. The installer is the one listed on the
postgresql support page. I think version 12.3 was installed the same
way but that was before I came into contact with this application
You need to make sure, mixing installation methods can
The server version is 2016. The installer is the one listed on the postgresql
support page. I think version 12.3 was installed the same way but that was
before I came into contact with this application Sent from my Verizon, Samsung
Galaxy smartphone
Original message From: Adria
On 8/3/22 10:16 AM, zaphod61 wrote:
I've inherited a postgresql 12.3 installation. It has 1 database in it.
I need to upgrade it to the newest version, which appears to be 12.11.
Can I just download the installer for 12
11 and run that to upgrade the product and still maintain access to the
> On Aug 3, 2022, at 10:16, zaphod61 wrote:
>
>
> I've inherited a postgresql 12.3 installation. It has 1 database in it. I
> need to upgrade it to the newest version, which appears to be 12.11. Can I
> just download the installer for 12
> 11 and run that to upgrade the product and still m
On Wednesday, August 3, 2022, zaphod61 wrote:
>
> I've inherited a postgresql 12.3 installation. It has 1 database in it. I
> need to upgrade it to the newest version, which appears to be 12.11. Can I
> just download the installer for 12
> 11 and run that to upgrade the product and still maintai
I've inherited a postgresql 12.3 installation. It has 1 database in it. I need
to upgrade it to the newest version, which appears to be 12.11. Can I just
download the installer for 1211 and run that to upgrade the product and still
maintain access to the existing connections?Sent from my Verizo
Thanks for the response, Tom. I think that's exactly what's going on here.
On Wed, Aug 3, 2022 at 11:28 AM Tom Lane wrote:
> Adrian Klaver writes:
> > On 8/3/22 08:09, Kevin Martin wrote:
> >> I thought that any UPDATE message in the replication logs is designed
> to
> >> include all values fo
jian he wrote:
> ./configure --with-perl --with-python --with-icu
> ICU_CFLAGS='-I/usr/include/unicode' ICU_LIBS='-L/usr/lib/icu'
> --enable-debug --with-pgport=5440
The location with -L is not sufficient in ICU_LIBS.
The list of libraries to link with should be put as well.
For instanc
Adrian Klaver writes:
> On 8/3/22 08:09, Kevin Martin wrote:
>> I thought that any UPDATE message in the replication logs is designed to
>> include all values for all columns. Is that correct?
Buried deep in the wire protocol specification is this bit:
The following message parts are shar
I had a look into what actually changed in the table. At the first
write that I grabbed, four rows in that segment had such a change:
117ee000 77 00 00 00 00 df b8 82 8e a4 00 00 64 00 a0 00 |w...d...|
117ee000 77 00 00 00 f0 22 b4 f3 68 d3 00 00 64 00 a0 00 |w"..h...d...|
117
My apologies. Read that in the mailing list instructions, and still
forgot. Thanks for the reminder.
On Wed, Aug 3, 2022 at 11:12 AM Adrian Klaver
wrote:
> On 8/3/22 08:09, Kevin Martin wrote:
>
> Please reply to list also
> Ccing list
>
> I don't have answers to below at the moment, just gett
On 8/3/22 08:09, Kevin Martin wrote:
Please reply to list also
Ccing list
I don't have answers to below at the moment, just getting thread back to
list so others who might have answers can see it.
Thanks for the reply, Adrian.
We're looking at the messages in the replication slot using
pg_
On 8/3/22 06:50, Kevin Martin wrote:
We have a replication slot set up on a database in Postgres 12.8. For
one of the tables, when a row is created, we see a series of records
come through - an INSERT followed by a handful of UPDATEs. All of these
messages in the WAL files show all columns, exc
We have a replication slot set up on a database in Postgres 12.8. For one
of the tables, when a row is created, we see a series of records come
through - an INSERT followed by a handful of UPDATEs. All of these messages
in the WAL files show all columns, except for the last UPDATE message,
which is
Hello,
this is postgres version 12.11_1 on Freebsd 13.1
I have a table "mess", filename "6309215", that behaves strange.
Data is currently only inserted/appended, there is no update and no
(successful) delete done, autovacuum is NOT enabled.
This is the definition:
CREATE TABLE IF NOT EXISTS
Then I try to install the latest from the latest source code.
./configure --with-perl --with-python --with-icu
ICU_CFLAGS='-I/usr/include/unicode' ICU_LIBS='-L/usr/lib/icu'
--enable-debug --with-pgport=5440
./configure.status return
config.status: creating GNUmakefile
> config.status: creating
27 matches
Mail list logo