Mark,
Look into kerberos. You will have to recompile your server to use it.
Bob Lunney
--- On Thu, 8/5/10, Mark Steben wrote:
> From: Mark Steben
> Subject: [ADMIN] password administration
> To: pgsql-admin@postgresql.org
> Date: Thursday, August 5, 2010, 3:58 PM
>
>
> Hi postgres gurus:
>
Following query would help you:
select inhparent::pg_catalog.regclass, inhrelid::pg_catalog.regclass from
pg_inherits;
Thanks & Regards,
Vibhor Kumar (PCP & OCP)
ITIL V3 Cerftified.
On Aug 5, 2010, at 7:11 PM, Kevin Kempter wrote:
> Hi All;
>
> can anyone point me to a system catalog query th
Hi All;
can anyone point me to a system catalog query that will show me the base table
name, and all partition table names for any table that has children
(inheritance) ?
Thanks in advance
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
Correcting I use LDAP + postgresql
2010/8/5 Victor Hugo :
> Mark,
>
> You could use LDAP to? that?
>
> I use LDAP + apache
>
> []´s
> Victor Hugo
>
>
>
> 2010/8/5 Tom Lane :
>> "Mark Steben" writes:
>>> I would like to set up a facility that enforces password changes for roles
>>> After a pre
Mark,
You could use LDAP to? that?
I use LDAP + apache
[]´s
Victor Hugo
2010/8/5 Tom Lane :
> "Mark Steben" writes:
>> I would like to set up a facility that enforces password changes for roles
>> After a predefined period (30 days for instance) when logging into psql
>> Or, at the very leas
Also, for reference:
http://research.microsoft.com/en-us/people/cormac/
Specifically:
http://research.microsoft.com/users/cormac/papers/2009/SoLongAndNoThanks.pdf
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/m
Scott Marlowe writes:
> On Thu, Aug 5, 2010 at 2:20 PM, Craig James
> wrote:
>> A better solution is to implement a password-strength algorithm and require
>> people to select decent passwords to begin with.
> Exactly. If you allow simpler passwords that have to be changed you
> get things lik
On Thu, Aug 5, 2010 at 2:27 PM, Scott Marlowe wrote:
> On Thu, Aug 5, 2010 at 2:20 PM, Craig James
> wrote:
>> On 8/5/10 12:58 PM, Mark Steben wrote:
>>>
>>> I would like to set up a facility that enforces password changes for roles
>>> After a predefined period (30 days for instance) when loggi
"Mark Steben" writes:
> I would like to set up a facility that enforces password changes for roles
> After a predefined period (30 days for instance) when logging into psql
> Or, at the very least, send an email out to notify that your current
> Password period is about to expire.
Usually we sug
On Thu, Aug 5, 2010 at 2:20 PM, Craig James wrote:
> On 8/5/10 12:58 PM, Mark Steben wrote:
>>
>> I would like to set up a facility that enforces password changes for roles
>> After a predefined period (30 days for instance) when logging into psql
>> Or, at the very least, send an email out to not
On 8/5/10 12:58 PM, Mark Steben wrote:
I would like to set up a facility that enforces password changes for roles
After a predefined period (30 days for instance) when logging into psql
Or, at the very least, send an email out to notify that your current
Password period is about to expire. Prefe
Hi postgres gurus:
I would like to set up a facility that enforces password changes for roles
After a predefined period (30 days for instance) when logging into psql
Or, at the very least, send an email out to notify that your current
Password period is about to expire. Preferably, I'd like to
Silvio ,
I had a similar problem when starting the database from an account that didn't
have the appropriate ulimits set. Check the ulimit values using ulimit -a.
HTH,
Bob Lunney
--- On Thu, 8/5/10, Silvio Brandani wrote:
> From: Silvio Brandani
> Subject: [ADMIN] out of memory error
> To
"xsun" writes:
> When the psql server is started under Linux platform, in /tmp directory
> there is a lock files named ".s.PGSQL..lock". So I want to know what
> is the function of this lock file?
It prevents multiple postmasters from trying to use the same socket file.
> And does the server w
2010/8/5 Silvio Brandani :
>>
>
> I have tried to increase the parameters but still fail. what is strange is
> that with psql the query works fine and give result immediatly, with
> application through odbc the query fail
That's usually the opposite of what you want to do here.
--
Sent via pgsql
hi..
we test locking PostgreSQL 8.4.4 on x86_64.
1> session 1
###
$ psql mydb
drop table citytest;
CREATE TABLE citytest (
i_id integer ,
city varchar(80)
) ;
ALTER TABLE citytest ADD CONSTRAINT citytest_pkey PRIMARY KEY (i_id);
insert into citytest values (1,'aaa');
i
When the psql server is started under Linux platform, in /tmp directory
there is a lock files named ".s.PGSQL..lock". So I want to know what
is the function of this lock file? And does the server work well without
this lock file?
Additionally, I know that the file ".s.PGSQL." is used as the uni
When the psql server is started under Linux platform, in /tmp directory
there is a lock files named ".s.PGSQL..lock". So I want to know what
is the function of this lock file? And does the server work well without
this lock file?
Additionally, I know that the file ".s.PGSQL." is used as the unix
d
Silvio Brandani writes:
>> "Kevin Grittner" writes:
>>> What query?
[ query with aggregates and GROUP BY ]
Does EXPLAIN show that it's trying to use a hash aggregation plan?
If so, try turning off enable_hashagg. I think the hash table might
be ballooning far past the number of entries the pla
Tom Lane ha scritto:
"Kevin Grittner" writes:
Silvio Brandani wrote:
a query on our production database give following errror:
2010-08-05 10:52:40 CEST [12106]: [278-1] ERROR: out of memory
2010-08-05 10:52:40 CEST [12106]: [279-1] DETAIL: Failed on
request of size 48.
"Kevin Grittner" writes:
> Silvio Brandani wrote:
>> a query on our production database give following errror:
>>
>> 2010-08-05 10:52:40 CEST [12106]: [278-1] ERROR: out of memory
>> 2010-08-05 10:52:40 CEST [12106]: [279-1] DETAIL: Failed on
>> request of size 48.
> What query? On what OS?
Victor Hugo ha scritto:
Hi Silvio,
I don't know if this is relevant. But, work_mem and some other
parameters inside postgresql.conf are not set. Here is a portion of
the file:
shared_buffers = 32MB
temp_buffers = 8MB
max_prepared_transactions = 5
work_mem = 1MB
maintenance_work_mem = 16MB
max_s
Silvio Brandani wrote:
> a query on our production database give following errror:
>
> 2010-08-05 10:52:40 CEST [12106]: [278-1] ERROR: out of memory
> 2010-08-05 10:52:40 CEST [12106]: [279-1] DETAIL: Failed on
> request of size 48.
What query? On what OS? Is this a 32-bit or 64-bit buil
Hi Silvio,
I don't know if this is relevant. But, work_mem and some other
parameters inside postgresql.conf are not set. Here is a portion of
the file:
shared_buffers = 32MB
temp_buffers = 8MB
max_prepared_transactions = 5
work_mem = 1MB
maintenance_work_mem = 16MB
max_stack_depth = 2MB
[]´s
Vi
Hi,
a query on our production database give following errror:
2010-08-05 10:52:40 CEST [12106]: [278-1] ERROR: out of memory
2010-08-05 10:52:40 CEST [12106]: [279-1] DETAIL: Failed on request of
size 48.
any suggestion ?
--
Silvio Brandani
Infrastructure Administrator
SDB Information
25 matches
Mail list logo
