Обсуждение: Re: [HACKERS] [PATCH] pgcrypto: pgp_encrypt v3

Поиск
Список
Период
Сортировка

Re: [HACKERS] [PATCH] pgcrypto: pgp_encrypt v3

От
Neil Conway
Дата:
Bruce Momjian wrote:
> Your patch has been added to the PostgreSQL unapplied patches list

That is not the latest version of Marko's patch. But in any case, the
patch is not yet ready for application:

http://archives.postgresql.org/pgsql-patches/2005-07/msg00077.php

-Neil

Re: [HACKERS] [PATCH] pgcrypto: pgp_encrypt v3

От
Marko Kreen
Дата:
On Tue, Jul 05, 2005 at 10:20:17AM +1000, Neil Conway wrote:
> Bruce Momjian wrote:
> >Your patch has been added to the PostgreSQL unapplied patches list
>
> That is not the latest version of Marko's patch.

Bruce got v3, thats indeed the latest.

Also, http://momjian.postgresql.org/cgi-bin/pgpatches shows v3.


> But in any case, the
> patch is not yet ready for application:
>
> http://archives.postgresql.org/pgsql-patches/2005-07/msg00077.php

Now I did fresh rebuild of CVS and played with it.  Result
is that it is only partly my error.  It just happens that I did
initdb with option '-E unicode'.  Now, can anybody explain the
following difference:

========================================
$ psql -c '\l' template1; psql -c "select 'a\nxxxxxx'::text as
x;" template1
           List of databases
        Name        | Owner | Encoding
--------------------+-------+-----------
 contrib_regression | marko | SQL_ASCII
 postgres           | marko | SQL_ASCII
 template0          | marko | SQL_ASCII
 template1          | marko | SQL_ASCII
(4 rows)

    x
----------
 a
xxxxxx
(1 row)
========================================
$ psql -c '\l' template1; psql -c "select 'a\nxxxxxx'::text as
x;" template1
           List of databases
        Name        | Owner | Encoding
--------------------+-------+----------
 contrib_regression | marko | UTF8
 postgres           | marko | UTF8
 template0          | marko | UTF8
 template1          | marko | UTF8
(4 rows)

 x
---
 a
xxxxxx
(1 row)

=========================================

I can send new regression test for SQL_ASCII, but it still
would not work for all users.

--
marko