Glyn Astill wrote:
> Maybe the docs should be embellished to also say "since a
> superuser is automatically considered a member of any group, it
> should be taken into account that names with a + mark will affect
> all superusers (although this was not the case prior to 9.0)" or
> something alon
> From: Kevin Grittner
>Glyn Astill wrote:
>
>> How can I specifically catch superusers?
>
> Create a group (nobody?) that you don't grant to any users. Only
> superusers will be a member of it.
>
Ah of course, simple, thanks Kevin.
I can't help but feel that there should be something in
A J wrote:
> Now I expect my DML statements to take atleast 100ms. But when I
> try to execute a few and measure using the timing command of
> postgres or the time command of linux, the duration is just a few
> milliseconds.
> What am I doing wrong ?
Have you changed commit_siblings from the
Glyn Astill wrote:
> How can I specifically catch superusers?
Create a group (nobody?) that you don't grant to any users. Only
superusers will be a member of it.
-Kevin
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postg
> From: Tom Lane
>G lyn Astill writes:
>> I'm having what's hopefully a fairly trivial issue here with
> pg_hba.conf in 9.0.4; when I add in the following line
>
>> host all +ad_users 10.10.0.0/16 ldap details>
>
>> If I try to log in with a superuser account
I am trying to see the impact of commit_delay.
Set it to 10 (microseconds), i.e. to 100ms
synchronous_commit is kept to default (i.e. ON)
Now I expect my DML statements to take atleast 100ms. But when I try to execute
a few and measure using the timing command of postgres or the time command
Glyn Astill writes:
> I'm having what's hopefully a fairly trivial issue here with pg_hba.conf in
> 9.0.4; when I add in the following line
> hostall +ad_users 10.10.0.0/16 ldap details>
> If I try to log in with a superuser account from the 10.10.0.0/16 network
Hi Guys,
I'm having what's hopefully a fairly trivial issue here with pg_hba.conf in
9.0.4; when I add in the following line
hostall +ad_users 10.10.0.0/16 ldap
If I try to log in with a superuser account from the 10.10.0.0/16 network it
appears to try to authen
On Wed, Jul 27, 2011 at 3:47 PM, Greg Smith wrote:
> On 07/22/2011 12:11 PM, A J wrote:
>
> Basically I wish my synchronous write transaction to not wait indefinitely
> when the synchronous standby servers are not available. But rather a
> response returned back to client that write could not be s
Hi all,
i have a Fedora repository which communicates with Postgresql.
I would like to have a High Availability solution for this scenario.
My first idea was, i use drbd on two VMs to synchronize both partions
and use Pacemaker to control the DRBD, IP, Fedora and Postgresql.
This part is done and
On 07/22/2011 12:11 PM, A J wrote:
Basically I wish my synchronous write transaction to not wait
indefinitely when the synchronous standby servers are not available.
But rather a response returned back to client that write could not be
successful, after trying for 'n' seconds. How can that be a
11 matches
Mail list logo
