ChoonSoo Park writes:
> Then I tried to test more complex thing - chained CA.
> Scenario 1. Postgresql having server.crt signed by Root CA and one of
> clients having postgresql.crt signed by intermediate CA.
> Machine 1: Created a new intermediate CA (ra.crt) signed by root
> certificate. Creat
Greetings,
I'm trying to setup SSL enabled postgresql environment. (PG: 9.1.6)
With a single root CA, everything works fine.
Machine 1: Create a self signed root certficate. Generate server
certificate (server.crt) & client certificate (postgresql.crt) signed by
the root certificate.
Machine 2 (P
elli...@cpi.com wrote:
> Hello,
>
> I have been running PostgreSQL for many months and just recently started
> getting this exception upon start up. Does anyone know what the issue
> might be?
>
> LOG: database system is ready to accept connections
> LOG: autovacuum launcher started
> LOG:
Hello,
I have been running PostgreSQL for many months and just recently started
getting this exception upon start up. Does anyone know what the issue
might be?
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
LOG: autovacuum launcher process was termina
On 10/30/2012 03:14 PM, David Johnston wrote:
"LIKE" is apparently not an operator but a special SQL construct.
Almost. :) The real problem is this, from the manual:
"The operator name is a sequence of up to NAMEDATALEN-1 (63 by default)
characters from the following list:
+ - * / < > = ~
> -Original Message-
> From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-
> ow...@postgresql.org] On Behalf Of Thalis Kalfigkopoulos
> Sent: Tuesday, October 30, 2012 3:55 PM
> To: pgsql-general@postgresql.org
> Subject: [GENERAL] overloading LIKE operator to handle integer + t
Hi all,
I'd like to be able to operate LIKE using as arguments an integer and
a text value.
In postgresql 9.0 the following raises an error:
# SELECT 123 LIKE '123';
ERROR: operator does not exist: integer ~~ unknown
LINE 1: select 123 like '123'; ^
HINT: No operator matches t
> -Original Message-
> From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-
> ow...@postgresql.org] On Behalf Of teleni...@gmail.com
> Sent: Tuesday, October 30, 2012 7:34 AM
> To: pgsql-general@postgresql.org
> Subject: [GENERAL] Average Balance "life"
>
> Hi there,
>
> Not su
Gurjeet Singh writes:
> On Tue, Oct 30, 2012 at 12:11 PM, Tom Lane wrote:
>> Gurjeet Singh writes:
>>> Is there a reason why Postgres chose to not use all lowercase characters
>>> for these parameters' names.
>> It's historical, for sure. I think we've discussed changing them and
>> decided it
On Tue, Oct 30, 2012 at 12:11 PM, Tom Lane wrote:
> Gurjeet Singh writes:
> > Is there a reason why Postgres chose to not use all lowercase characters
> > for these parameters' names.
> > DateStyle
> > IntervalStyle
> > TimeZone
>
> It's historical, for sure. I think we've discussed changing
Fantastic resource. Thanks for this!
On Tue, Oct 30, 2012 at 3:16 PM, Adrian Klaver wrote:
> On 10/30/2012 04:07 AM, RAJDEEP SARDAR wrote:
>
>> Dear All,
>>
>> I am a Mtech Student,IIT Bombay,India.
>>
>> I am having a database course project where I need to make some
>> modification in postgresq
Gurjeet Singh writes:
> Is there a reason why Postgres chose to not use all lowercase characters
> for these parameters' names.
> DateStyle
> IntervalStyle
> TimeZone
It's historical, for sure. I think we've discussed changing them and
decided it would be more likely to break things than impr
If you failed to solve your problem after following below 2 links,
http://1stopit.blogspot.dk/2011/01/postgresql-83-and-84-fails-to-install.html
http://igordcard.blogspot.dk/2012/03/unable-to-write-inside-temp-environment.html
try following last solution which will 100% work: (in my case it worke
On 10/30/2012 04:07 AM, RAJDEEP SARDAR wrote:
Dear All,
I am a Mtech Student,IIT Bombay,India.
I am having a database course project where I need to make some
modification in postgresql.
currently,my objective is to find how a select query runs in
postgresql.I have some knowledge related to pa
Dear All,
I am a Mtech Student,IIT Bombay,India.
I am having a database course project where I need to make some modification in
postgresql.
currently,my objective is to find how a select query runs in postgresql.I have
some knowledge related to parsing after going through some document upload
Hi there,
Not sure if this is the right place to post this question:
I'm tryting to find a way to do the following without going row by row on the
client program doing the calculations:
I've got a "movements" table (from an accounting program) for which I've
already done monthly balances and r
The fuzzystrmatch module (
http://www.postgresql.org/docs/9.2/static/fuzzystrmatch.html) is currently,
as of 9.2.1, documented with the caution *"At present, the soundex,
metaphone, dmetaphone, and dmetaphone_alt functions do not work well with
multibyte encodings (such as UTF-8)"*.
While the vene
Hi Kevin,
I think you are right. We need to use the connection pool for
all clients, so we can limit the number of active database
connections.
We have some legacy applications that is hard to change, but
we will have to do it.
Thanks a lot
Hi:
I am now reading the bgwriter.c’s source code, and found :
pqsignal(SIGHUP, BgSigHupHandler); /* set flag to read config file */
So I tried to use Kill –s SIGHUP to confirm it.
I found that if I directly send SIGHUP to bgwriter, it has no response.
If I send SIGHUP to its parent—postgres, I
On 10/30/12 12:32 AM, Frank Lanitz wrote:
I was maintaining a setup which had > 1000 connections on a not very
high-end server (12GB of Ram). It was just most of the connections were
idling most the time. Tomcat with a high number of consistent
connections for some reasons and end user stand alon
Am 30.10.2012 02:06, schrieb rodr...@paripassu.com.br:
> BTW, 200 seems alwfully high unless a *really* high end machine. Â You
>> may have fewer timeouts if you avoid swamping the server with a
>> "thundering herd" of requests.
I was maintaining a setup which had > 1000 connections on a not very
21 matches
Mail list logo
