On Fri, Jan 30, 2015 at 9:54 AM, Day, David wrote:
>
> Alan,
>
>
>
> I tried as you suggested, I believe the gdb debugger is giving some false
> indication about threads.
>
> Whether I attach to a newly launched backend or a backend that has been
> executing the suspect perlu function.
>
> The
On 31 January 2015 at 06:42, Steve Boyle wrote:
> Thanks for the hint. I found a config error, I had added the host=
> param with the bdr.nodename_local_replica_dsn entry. Sorting out the
> bdr.nodename_local_replica_dsn entry solved my issue.
>
>
Glad to hear it.
--
Craig Ringer
On 1/29/2015 2:12 PM, Israel Brewster wrote:
I'm working on setting up a new PostgreSQL database server, and would
like to be able to monitor a number of statistics on it, such as:
number of connections
number of queries
query times
etc.
All these stats are easily available, either from the
p
Ok thanks for the advice John - much appreciated.
From: pgsql-general-ow...@postgresql.org [pgsql-general-ow...@postgresql.org]
On Behalf Of John R Pierce [pie...@hogranch.com]
Sent: Friday, 30 January 2015 10:33 p.m.
To: pgsql-general@postgresql.org
Subjec
On Jan 29, 2015, at 1:20 PM, Michael Heaney wrote:
> On 1/29/2015 5:12 PM, Israel Brewster wrote:
>> I'm working on setting up a new PostgreSQL database server, and would like
>> to be able to monitor a number of statistics on it, such as:
>>
>> number of connections
>> number of queries
>> que
Thanks for the hint. I found a config error, I had added the host= param with
the bdr.nodename_local_replica_dsn entry. Sorting out the
bdr.nodename_local_replica_dsn entry solved my issue.
Thanks!
From: Craig Ringer [mailto:cr...@2ndquadrant.com]
Sent: Thursday, January 29, 2015 5:00 PM
To:
On Fri, 30 Jan 2015 09:30:31 -0600
Jeff Amiel wrote:
> Probably temp table related ...but catalog bloat on one of my databases
> appears to be pretty bad.
>
> Is the below bloat (table and index) something to worry about?
> pg_stat_all_tables show the relations ARE getting successfully vacuumed.
Alan,
I tried as you suggested, I believe the gdb debugger is giving some false
indication about threads.
Whether I attach to a newly launched backend or a backend that has been
executing the suspect perlu function.
The “info threads” result is two. Suspiciously they are both at the same
lo
It's not real deep, but it was interesting to me as an answer to "what is
this anyway?" I've not really looked at HSTORE or JSONB due to other
interests at present.
http://www.linuxjournal.com/content/postgresql-nosql-database
--
He's about as useful as a wax frying pan.
10 to the 12th power
On 30/01/2015 14:46, Adrian Klaver wrote:
> On 01/30/2015 01:16 AM, Ramesh T wrote:
>> when i try to dump the database windows based pgadmin 3 it returns
>> message like
>>
>> pg_dump: server version: 9.3.4; pg_dump version: 9.1.3
>> pg_dump: aborting because of server version mismatch
>>
>> any he
Probably temp table related ...but catalog bloat on one of my databases
appears to be pretty bad.
Is the below bloat (table and index) something to worry about?
pg_stat_all_tables show the relations ARE getting successfully vacuumed...
Any suggestions on eliminating? Not sure if tools like pg_re
I always have a single row in these selects so the result will have only
a row.
I must make a single select for a framework that takes as parameter a
single select to complete a XML template in a particular situation.
-- Original Message --
From: "John R Pierce"
To: pgsql-general@postgre
On 01/30/2015 01:16 AM, Ramesh T wrote:
when i try to dump the database windows based pgadmin 3 it returns
message like
pg_dump: server version: 9.3.4; pg_dump version: 9.1.3
pg_dump: aborting because of server version mismatch
any help..?
Use a 9.3+ version of pg_dump. A version of pg_dump i
On Thursday, January 29, 2015 10:14 PM, Adrian Klaver wrote:
> On 01/29/2015 04:36 AM, holger.friedrich-fa-triva...@it.nrw.de wrote:
>> Hello list,
>> What are your experiences with OpenSCG's RPM packages?
[deletia]
> From what I gather it is static binary package built against libraries at a
>
On 1/30/2015 12:31 AM, Jeremy Palmer wrote:
The PostgreSQL DB is currently setup with Kerberos for Windows SSO, as well as
MD5 password authentication for another pool of other PostgreSQL users who are
not part of our Active Directory. LDAP could be used, but then we would have to
move the cur
David G Johnston wrote
> Personally, I would consider having both Apache and PostgreSQL talk to a
> LDAP database if you really need to have a single point of identity
> definition.
The PostgreSQL DB is currently setup with Kerberos for Windows SSO, as well as
MD5 password authentication for an
16 matches
Mail list logo