Well, all the data is inserted and used by JDBC (other libraries on top of
JDBC, in fact), and it is all working perfectly for months. I can update
and/or read data through JDBC or pgAdmin, and the change is correctly
reflected on the other.The first TEXT columns I used store text files around
50k,
pgAdmin doesn't know what it's opening until it looks at it - and as a
one-line config file with a single include directive or comment is
technically valid, and we intentionally don't hard-code the allowable
directives into pgAdmin (consider user defined GUCs for add-on
modules), it's not complet
On Thu, Oct 1, 2009 at 10:02 AM, Andrus wrote:
>> Unless you're running pgAdmin directly on the server, you can't I'm
>
> afraid. This is a security restriction in the adminpack contrib module
> in PostgreSQL itself.
>
> postgresql superuser has access to those files. So this is is a bug:
> implem
Unless you're running pgAdmin directly on the server, you can't I'm
afraid. This is a security restriction in the adminpack contrib module
in PostgreSQL itself.
postgresql superuser has access to those files. So this is is a bug:
implementation restricts access granted by Linux file system.
Al
2009/10/1 Andrus :
> Debian server standard installation places pg_hba.conf, pg_ident.conf,
> postgresql.conf , start.conf files to /etc/postgresql/8.3/data
> Database cluster is in /var/lib/postgresql/8.3/data
>
> Trying to edit pg_hba.conf and postgresql.conf from pgAdmin 1.10.0 from
> windows
Debian server standard installation places pg_hba.conf, pg_ident.conf,
postgresql.conf , start.conf files to /etc/postgresql/8.3/data
Database cluster is in /var/lib/postgresql/8.3/data
Trying to edit pg_hba.conf and postgresql.conf from pgAdmin 1.10.0 from
windows causes errors and shows em
