Hello,
I have found the reason. It is due to an update of cpanel. According to its
author, to "automatically secures the pg_hba.conf file":
http://forums.cpanel.net/f354/cpanel-update-changed-pg_hba-conf-samerole-338982.html
Thank you very much.
Look at the timestamp of when this file [pg_hba.conf] is updated and see if
there is any correlation to system messages [/var/log/messages or
equivalent of your kernel].
Thanking you,
Prashanth Kumar Goriparthi
Mobile : 312 316 4396
On Fri, May 3, 2013 at 10:13 AM, Fred Parkinson wrote:
> Wou
Would it make sense to make the file read-only and see if a write error pops up
somewhere?
Fred
>>> Nghia Truong 05/03/2013 8:59 AM >>>
Hi all,
I am the root user (except that my dedicated server is under the control of its
company). I don't have any sysadmin script. The problem just suddenl
On Fri, May 03, 2013 at 10:59:09PM +0700, Nghia Truong wrote:
> Hi all,
> I am the root user (except that my dedicated server is under the control of
> its company). I don't have any sysadmin script. The problem just suddenly
> occurs. I don't know why?
as best i know, with the standard postgresql
Hi all,
I am the root user (except that my dedicated server is under the control of
its company). I don't have any sysadmin script. The problem just suddenly
occurs. I don't know why?
Nghia T. Truong
On Fri, May 3, 2013 at 10:52 PM, Johnny T
Chef/Puppet?
On Fri, May 3, 2013 at 10:28 AM, Ray Stell wrote:
>
> On May 3, 2013, at 9:45 AM, Nghia Truong wrote:
>
> Hi everyone,
> Every day, the file pg_hba.conf in my server is rewritten and postgresql
> received
> a SIGHUP to reload configuration.
>
>
> Sounds like some sysadmin scripted
default_transaction_read_only is just a default. Users can still disable it
for themselves and it is not intended to act as a security measure. In the
second example, user uuu could still create and modify data for which s/he
has the privileges granted to do so by first issuing a "set transaction
r
Hi, guys.
Postgres doc says it is better to place the pgstat.stat file in ram disk.
And it says that at shutdown, it is copied to global.
What happens if postgres do not shutdown the usual way?
If machine loses power, for example...
On May 3, 2013, at 9:45 AM, Nghia Truong wrote:
> Hi everyone,
> Every day, the file pg_hba.conf in my server is rewritten and postgresql
> received a SIGHUP to reload configuration.
Sounds like some sysadmin scripted rsync gone wild.
Hi , i dont expert in postrgres , but i'll checked why
This server reload configuration every day ?
after
Set permission the file on the her user and check the application client ,
maybe has a new file or instrutions for rewritten
may solv !
De: pgsql-admin-ow...@postgresql.org [mailto:
Hello,
Usually I would
create user uuu password 'ppp';
GRANT usage on schema zzz to uuu;
GRANT select on all tables in schema zzz to uuu;
But just this morning someone used
create user uuu password 'ppp';
alter user uuu set default_transaction_read_only = on;
GRANT select on all tables in sch
Hi everyone,
Every day, the file pg_hba.conf in my server is rewritten and
postgresql received
a SIGHUP to reload configuration. The pg_hba.conf content is:
=
...
..
local samerole allmd5
host samerole all 127.0.0.1 255.255.255.255 m
12 matches
Mail list logo
