Re: [HACKERS][REVIEW]: Password identifiers, protocol aging and SCRAM protocol

: first we need to apply patches 0001-0008, then 0009. Then, all patches were successfully compiled. All test passed. -- Regards, Valery Popov Postgres Professional http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org

Re: [HACKERS][REVIEW]: Password identifiers, protocol aging and SCRAM protocol

ier_type = 'class="PARAMETER">password' like this PASSWORD VERIFIERS ( class="PARAMETER">verifier_type = 'class="PARAMETER">password'-- Regards, Valery Popov Postgres Professional http://www.postgrespro.com The Russian Postgres Co

Re: [HACKERS][REVIEW]: Password identifiers, protocol aging and SCRAM protocol

+1. On 03/02/2016 02:55 PM, Michael Paquier wrote: On Wed, Mar 2, 2016 at 5:43 PM, Valery Popov wrote: So the markup is missing. Thanks. I am taking note of it. -- Regards, Valery Popov Postgres Professional http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hacker

Re: [HACKERS] Password identifiers, protocol aging and SCRAM protocol

installcheck-world, Thanks. -- Regards, Valery Popov Postgres Professional http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Password identifiers, protocol aging and SCRAM protocol

it is not necessary to be an authenticated user, so if there are bugs in it it would be possible for example to crash down Postgres just by sending authentication requests. -- Regards, Valery Popov Postgres Professional http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hacke

Re: [HACKERS] Password identifiers, protocol aging and SCRAM protocol

26.02.2016 01:10, Michael Paquier пишет: On Fri, Feb 26, 2016 at 1:38 AM, Valery Popov wrote: Hi, Michael 23.02.2016 10:17, Michael Paquier пишет: Attached is a set of patches implementing a couple of things that have been discussed, so let's roll in. Those 4 patches are aimed at pu

[HACKERS] [PROPOSAL] Max recursion depth in WITH Queries (Common Table Expressions)

MAXRECURSION hint for the same purpose. Thanks! -- Regards, Valery Popov Postgres Professional http://www.postgrespro.com The Russian Postgres Company diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 1da7dfb..33a6009 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/sr

Re: [HACKERS] [PROPOSAL] Max recursion depth in WITH Queries (Common Table Expressions)

28.10.2015 16:33, Tom Lane пишет: Valery Popov writes: Recursive queries are typically used to deal with hierarchical or tree-structured data. In some conditions when data contain relationships with cycles recursive query will loop unlimited and significantly slows the client's se