Thanks, I have considered it, and I'd like to stick with an array for
my use case if possible. Also, if citext is being advised against, I'd
like to know about it, since I use it extensively and have never had
an issue with it. Can anyone shed some light on this?
Thanks!
Chris
On Sat, Aug 16, 201
Have you considered normalizing?
Here's a SQLFiddle example: http://sqlfiddle.com/#!15/61897/3/0. It uses
text instead of citext, but I imagine your results should be similar. Also,
I think usage of citext is generally recommended against.
The basic idea is to not use an array but use a second ta
On 08/16/2014 12:26 PM, Redoute wrote:
Hello,
log destination is configured as stderr, with logging collector on
(default setup). So it may be one issue that stderr is written in 1252
(not sure about that), but then why are most logfile entries encoded in
UTF-8? Is only a part of all message
On 08/16/2014 12:26 PM, Redoute wrote:
Hello,
please help me with this problem: My postgreSQL logfiles generally are
encoded in UTF-8, but some entries are in Windows-1252. The server
status in pgAdmin III doesn't cope with this; it is unusable because of
continuous error popups.
log destinat
On 08/16/2014 07:47 AM, Matt Silverlock wrote:
Hi all.
Trying to rationalise my pg_hba.conf and pg_ident.conf configuration on
a Debian/Ubuntu machine where:
* One primary application user (“deploy”) runs web applications
* postgres, nginx, et. al run under their own users
* Using a Unix socket
Redoute writes:
> please help me with this problem: My postgreSQL logfiles generally are
> encoded in UTF-8, but some entries are in Windows-1252. The server
> status in pgAdmin III doesn't cope with this; it is unusable because of
> continuous error popups.
> I found several discussions regardin
Hello,
please help me with this problem: My postgreSQL logfiles generally are
encoded in UTF-8, but some entries are in Windows-1252. The server
status in pgAdmin III doesn't cope with this; it is unusable because of
continuous error popups.
I found several discussions regarding this issue, e. g.
John R Pierce writes:
> On 8/16/2014 9:16 AM, Steve Atkins wrote:
>> Setting environment variables to point to your preferred instance will also
>> work - and it'll work with any client that uses libpq (which is probably
>> almost everything that's not java).
> java/jdbc doesn't support unix do
On 8/16/2014 9:16 AM, Steve Atkins wrote:
Setting environment variables to point to your preferred instance will also
work - and it'll work with any client that uses libpq (which is probably almost
everything that's not java).
java/jdbc doesn't support unix domain sockets anyways, so that's m
On Aug 16, 2014, at 9:01 AM, Nick Guenther wrote:
>
>
> On August 16, 2014 11:41:02 AM EDT, lin wrote:
>> Hi all,
>> I change the value of "unix_socket_directories" in postgresql.conf ,
>> then restart the database, but it cannot connect the database used like
>> this
>> "psql -d postgres -
On 8/16/2014 9:01 AM, Nick Guenther wrote:
First thing to point out is that you need only one of -h and -p. They are
redundant options, because you only connect to postgres either over TCP (-p) or
with a unix domain socket (-h).
what??!? no, this is totally wrong.
psql -h myserver -p
On August 16, 2014 11:41:02 AM EDT, lin wrote:
>Hi all,
>I change the value of "unix_socket_directories" in postgresql.conf ,
>then restart the database, but it cannot connect the database used like
>this
>"psql -d postgres -p 5432" , it must given the parameter " -h /xx/xx"
>to use the Unix
On Aug 16, 2014, at 8:49 AM, John R Pierce wrote:
> On 8/16/2014 8:41 AM, lin wrote:
>> I change the value of "unix_socket_directories" in postgresql.conf , then
>> restart the database, but it cannot connect the database used like this
>> "psql -d postgres -p 5432" , it must given the paramete
Le 16 août 2014 17:44, "lin" a écrit :
>
> Hi all,
> I change the value of "unix_socket_directories" in postgresql.conf ,
then restart the database, but it cannot connect the database used like
this
> "psql -d postgres -p 5432" , it must given the parameter " -h /xx/xx" to
use the Unix doma
On 8/16/2014 8:41 AM, lin wrote:
I change the value of "unix_socket_directories" in postgresql.conf ,
then restart the database, but it cannot connect the database used
like this
"psql -d postgres -p 5432" , it must given the parameter " -h /xx/xx"
to use the Unix domain socket。
how to fix thi
Hi all,
I change the value of "unix_socket_directories" in postgresql.conf , then
restart the database, but it cannot connect the database used like this
"psql -d postgres -p 5432" , it must given the parameter " -h /xx/xx" to use
the Unix domain socket。
how to fix this issue ?
th
Hi all.
Trying to rationalise my pg_hba.conf and pg_ident.conf configuration on a
Debian/Ubuntu machine where:
* One primary application user (“deploy”) runs web applications
* postgres, nginx, et. al run under their own users
* Using a Unix socket for connecting to PostgreSQL on the same machin
17 matches
Mail list logo
