Re: [GENERAL] [HACKERS] SSL and Encryption

On 11/2/2017 10:12 PM, Jeff Janes wrote: https://wiki.postgresql.org/wiki/List_of_drivers What is 'python native'?  psycopg works as long you update your libpq. I thought pythonistas preferred using a native driver that didn't use libpq ? -- john r pierce, recycling bits in santa cruz

Re: [GENERAL] [HACKERS] SSL and Encryption

On Thu, Nov 2, 2017 at 9:58 PM, John R Pierce wrote: > On 11/2/2017 9:39 PM, Michael Paquier wrote: > > The SCRAM discussion is spread across two threads mainly with hundreds > of emails, which may discourage even the bravest. Here are links to > the important >

Re: [GENERAL] [HACKERS] SSL and Encryption

On 11/2/2017 9:39 PM, Michael Paquier wrote: The SCRAM discussion is spread across two threads mainly with hundreds of emails, which may discourage even the bravest. Here are links to the important documentation: https://www.postgresql.org/docs/current/static/auth-methods.html#auth-password so

Re: [GENERAL] [HACKERS] SSL and Encryption

On Fri, Nov 3, 2017 at 3:19 AM, Craig Ringer wrote: > This is probably off topic for pgsql-hackers. > > For password crypto please go read the SCRAM thread and the PostgreSQL > 10 release notes. The SCRAM discussion is spread across two threads mainly with hundreds of

Re: [GENERAL] [HACKERS] SSL and Encryption

On 3 November 2017 at 11:16, chiru r wrote: > Hi , > > Please suggest the best chiper suite to configure openSSL for PostgreSQL > Server and client?. > > How to use other than md5 encryption algorithm to encrypt the passwords in > PostgreSQL? This is probably off topic for

[GENERAL] SSL and Encryption

Hi , Please suggest the best chiper suite to configure openSSL for PostgreSQL Server and client?. How to use other than md5 encryption algorithm to encrypt the passwords in PostgreSQL? Thanks, Chiru

Re: [GENERAL] checkpoint and recovering process use too much memory

Hi, On 2017-11-03 01:43:32 +, tao tony wrote: > I had an asynchronous steaming replication HA cluster.Each node had 64G > memory.pg is 9.6.2 and deployed on centos 6. > > > Last month the database was killed by OS kernel for OOM,the checkpoint > process was killed. > > > I noticed

Re: [GENERAL] checkpoint and recovering process use too much memory

On Fri, Nov 03, 2017 at 01:43:32AM +, tao tony wrote: > I had an asynchronous steaming replication HA cluster.Each node had 64G > memory.pg is 9.6.2 and deployed on centos 6. > > Last month the database was killed by OS kernel for OOM,the checkpoint > process was killed. If you still have

[GENERAL] checkpoint and recovering process use too much memory

hi dears, I had an asynchronous steaming replication HA cluster.Each node had 64G memory.pg is 9.6.2 and deployed on centos 6. Last month the database was killed by OS kernel for OOM,the checkpoint process was killed. I noticed checkpoint process occupied memory for more than 20GB，and it

Re: [GENERAL] EXPLAIN command just hangs...

On Thu, Nov 02, 2017 at 09:13:05PM +, Rhhh Lin wrote: > Yes, it may be an issue with the index, but I'd like to have some evidence > towards that before dropping and recreating (It does not appear that bloat is > a problem here or dead tuples either). Why do you say those aren't an issue?

Re: [GENERAL] EXPLAIN command just hangs...

Rhhh Lin writes: > The EXPLAIN statement is currently 'f' for waiting and 'active' via > pg_stat_activity, so it is doing something. The ps command does not show me > anything more verbose. ps would confirm for sure whether it was eating CPU time, whereas I do not

Re: [GENERAL] EXPLAIN command just hangs...

Thanks for replying Justin. Yes, it may be an issue with the index, but I'd like to have some evidence towards that before dropping and recreating (It does not appear that bloat is a problem here or dead tuples either). The EXPLAIN statement is currently 'f' for waiting and 'active' via

Re: [GENERAL] EXPLAIN command just hangs...

On Thu, Nov 02, 2017 at 08:51:23PM +, Rhhh Lin wrote: > However, this query will run for days without completing. I suspect it has to > do with the timestamp predicate and lack of using an appropriate index access > path. This is what I need to verify/establish. Perhaps the timestamp index

[GENERAL] EXPLAIN command just hangs...

Hi all, version = Postgres 9.3.10 I have a table with approx. 5 million rows. It is defined something like the below. col: type: timestamp bigint measurement_id integer value numeric(24,5) minval numeric(24,5) maxval numeric(24,5) There are two BTree indexes in place on the PK ("timestamp",

Re: [GENERAL] syntax error

I have figured it out. Thanks for thinking -- Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Building tds_fdw Extension for Windows 64bit

"Igal @ Lucee.org" writes: > So now I am getting the errors below.  Do I need to add an entry in > _deffile_ for each error message?  What does the entry look like? These look like you're failing to link to whatever library supplies dbbind() etc. Can't help you more than that.

Re: [GENERAL] Logical decoding error

On Thu, Nov 2, 2017 at 9:59 AM, Steve Atkins wrote: > > Where are the errors coming from - your code or pgx? If it's from pgx, > what's the exact error? ('w' is regular replication payload data, so it'd > be expected as a copydata payload message type, but would be an error

Re: [GENERAL] Building tds_fdw Extension for Windows 64bit

On 11/2/2017 8:40 AM, Tom Lane wrote: It looks to me like MSVC is complaining about the PGDLLEXPORT markings that tds_fdw.c has on the function definitions (not the extern declarations). In the core code we only put PGDLLEXPORT in extern declarations ... so try keeping it in the externs and

Re: [GENERAL] Logical decoding error

> On Nov 2, 2017, at 9:34 AM, Mark Fletcher wrote: > > Hello, > > Running Postgres 9.6.5, we're using logical decoding to take changes to the > database and propagate them elsewhere in our system. We are using the PGX Go > Postgres library, at

[GENERAL] syntax error

Hi, I am setting up PostgreSQL standby on windows for the first time on version 9.4.14: Is the below syntax correct in the recovery.conf file restore_command = 'copy "D:\\apps\postgres\\pg_archivelog\\%f" "%p"' archive_cleanup_command = 'pg_archivecleanup "D:\\apps\postgres\pg_archivelog\\"

[GENERAL] Logical decoding error

Hello, Running Postgres 9.6.5, we're using logical decoding to take changes to the database and propagate them elsewhere in our system. We are using the PGX Go Postgres library, at https://github.com/jackc/pgx, and we are using the test_decoding plugin to format the changes. We are using 6

Re: [GENERAL] Building tds_fdw Extension for Windows 64bit

"Igal @ Lucee.org" writes: > Any other ideas? It looks to me like MSVC is complaining about the PGDLLEXPORT markings that tds_fdw.c has on the function definitions (not the extern declarations). In the core code we only put PGDLLEXPORT in extern declarations ... so try keeping

Re: [GENERAL] Building tds_fdw Extension for Windows 64bit

On 11/2/2017 1:05 AM, Laurenz Albe wrote: Igal @ Lucee.org wrote: After reading Craig's excellent blog post at https://blog.2ndquadrant.com/compiling-postgresql-extensions-visual-studio-windows/ I decided to try and build a real extension - tds_fdw. I've set it up in Visual Studio Community

Re: [GENERAL] Building tds_fdw Extension for Windows 64bit

Igal @ Lucee.org wrote: > After reading Craig's excellent blog post at > https://blog.2ndquadrant.com/compiling-postgresql-extensions-visual-studio-windows/ > I decided to try and build a real extension - tds_fdw. > I've set it up in Visual Studio Community 2017, but am getting the following >

[GENERAL] Building tds_fdw Extension for Windows 64bit

Hello, After reading Craig's excellent blog post at https://blog.2ndquadrant.com/compiling-postgresql-extensions-visual-studio-windows/ I decided to try and build a real extension - tds_fdw. I've set it up in Visual Studio Community 2017, but am getting the following errors: Error