Dear list,
in dbmail there's a query that worked until postgresql 8.2 (i stripped
the unneeded parts for other tables):
SELECT k.messageblk FROM dbmail_messageblks k WHERE k.messageblk ILIKE
'%multipart/encrypted%';
In 8.3, you get an error
[ERROR: operator does not exist: bytea ~~* unknow
Hello,
I made a mistake an got a character set in SQL_ASCII as the defaut
encoding type :
$ psql -l
List of databases
Name | Owner | Encoding
--+--+---
cmp_crm | openerp | SQL_ASCII
cmp_crm_demo | openerp | SQL_ASCII
cmp_testcrm | op
On Thu, Sep 10, 2009 at 7:08 PM, Nicolas Michel wrote:
> Hello,
>
> I made a mistake an got a character set in SQL_ASCII as the defaut encoding
> type :
>
> $ psql -l
> List of databases
> Name | Owner | Encoding
> --+--+---
> cmp_crm | openerp
Michael Monnerie writes:
> in dbmail there's a query that worked until postgresql 8.2 (i stripped
> the unneeded parts for other tables):
> SELECT k.messageblk FROM dbmail_messageblks k WHERE k.messageblk ILIKE
> '%multipart/encrypted%';
> In 8.3, you get an error
There has *never* been a P
Greetings,
I am using versions 7.4 and 8.3.7.
I have not discovered a way to obfuscate the password when changing it
in psql with ALTER USER syntax.
The password displays in clear text at the command line AND in the log file.
Why is this?
Or am I missing something obvious in the documentation?
Tha
The documentation for 8.3 states:
ALTER USER is now an alias for ALTER ROLE.
Under the entry for ALTER ROLE it says:
Caution must be exercised when specifying an unencrypted password with
this command. The password will be transmitted to the server in
cleartext, and it might also be logged i
Lewis Kapell writes:
> ... psql contains a command \password that can be used
> to safely change a role's password.
FWIW, all that's doing is pre-encrypting the password and sending
ALTER ROLE WITH ENCRYPTED PASSWORD '...';
regards, tom lane
--
Sent via pgsql-admin mai
hi all,
since several days I try to import some ascii data into my postgresql 8.4
(under Win Vista SP1) database.
I use the copy command under pgAdmin III. This is some example data (from an
UTF-8 encoded textfile):
1| 3.721E-01| 1.000E+00|S
2| 1.240E+00| 1.000E+01|S
3| 9.417E
The problem is solved. It may be helpful for other text encoding newbies like
me that many
Windows Applications (and the .NET classes by default) create a byte order mark
(bom) when
they save data in utf-8 format. This bom is not accepted by the postgresql 8.4
copy command.
The editor notepad++
Greetings,
I am using versions 7.4 and 8.3.7.
I have not discovered a way to obfuscate the password when changing it
in psql with ALTER USER syntax.
The password displays in clear text at the command line AND in the log file.
Why is this?
Or am I missing something obvious in the documentation?
Than
Kenneth Banyas wrote:
> Greetings,
>
> I am using versions 7.4 and 8.3.7.
> I have not discovered a way to obfuscate the password when changing it
> in psql with ALTER USER syntax.
> The password displays in clear text at the command line AND in the log file.
> Why is this?
Perhaps you could try
Hi all;
How / where can I find which tablespace the indexes live in?
Thanks in advance
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
12 matches
Mail list logo