Hi,
I am trying to generate self-signed certificate for full ssl authentication. I
need to have universal version of this certificate for development purposes (so
any client can connect with any postgresql server with ssl on and verify-full
flag).
I am using IP while connecting, I mean host=.
Please Have a look on pg_stat_user_tables, there is a field called n_live_tup
.
But I think in some cases this might not hold the actual row number
Regards
From: Carlos Sotto Maior (SIM)
To: David Johnston ; pgsql-general@postgresql.org
Sent: Mon, May
On 31/05/11 15:40, Asia wrote:
> Would you please advise what I am doing wrong? Or maybe there is other way to
> generate wildcard certificate ? Or maybe this is a possible bug?
I wouldn't be surprised if libpq didn't support wildcard certificates at
all. I doubt there's ever been any demand for
On Tue, May 31, 2011 at 10:06, Craig Ringer wrote:
> On 31/05/11 15:40, Asia wrote:
>
>> Would you please advise what I am doing wrong? Or maybe there is other way
>> to generate wildcard certificate ? Or maybe this is a possible bug?
>
> I wouldn't be surprised if libpq didn't support wildcard c
On Tue, 31 May 2011 06:09:18 +0200
Pavel Stehule wrote:
>2011/5/31 Tarlika Elisabeth Schmitz :
>> On Mon, 30 May 2011 11:02:34 +0200
>> Pavel Stehule wrote:
>>
2) I took from your blog entry
(http://okbob.blogspot.com/2008/06/execute-using-feature-in-postgresql-84.html)
that it is
2011/5/31 Tarlika Elisabeth Schmitz :
> On Tue, 31 May 2011 06:09:18 +0200
> Pavel Stehule wrote:
>
>>2011/5/31 Tarlika Elisabeth Schmitz :
>>> On Mon, 30 May 2011 11:02:34 +0200
>>> Pavel Stehule wrote:
>>>
> 2) I took from your blog entry
> (http://okbob.blogspot.com/2008/06/execute-usi
On Tue, May 31, 2011 at 12:44, Asia wrote:
>
>
> W dniu 2011-05-31 11:09:10 użytkownik Magnus Hagander
> napisał:
>> On Tue, May 31, 2011 at 10:06, Craig Ringer
>> wrote:
>> > On 31/05/11 15:40, Asia wrote:
>> >
>> >> Would you please advise what I am doing wrong? Or maybe there is other
>> >
2011/5/31 Toby Corkindale :
> On 30/05/11 20:41, Cédric Villemain wrote:
>>
>> 2011/5/30 Toby Corkindale:
>>>
>>> On 28/05/11 18:42, Carl von Clausewitz wrote:
a few months ago, when I installed my first PostgreSQL, I have had the
same problem. I've try to get any information about o
2011/5/28 Carl von Clausewitz :
> Hi Preetika,
> a few months ago, when I installed my first PostgreSQL, I have had the same
> problem. I've try to get any information about optimal memory config, and
> working, but there wasn't any "optimal memory setting calculator" on the
> internet, just some g
Got it. Changing LC_CTYPE to " English_United States.1252" restores the
correct behavior.
Thanks.
David J.
> -Original Message-
> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
> Sent: Monday, May 30, 2011 10:40 PM
> To: David Johnston
> Cc: pgsql-general@postgresql.org
> Subject: Re: [GENE
This message has been digitally signed by the sender.
Re___GENERAL__Regular_disk_activity_of_an_idle_DBMS.eml
Description: Binary data
Hi-Tech Gears Ltd, Gurgaon, India
Sent using "PostMaster" by QuantumLink Communications
Get your
> -Original Message-
> From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-
> ow...@postgresql.org] On Behalf Of Tom Lane
> Sent: Monday, May 30, 2011 11:10 PM
> To: David Johnston
> Cc: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] Function Column Expansion Causes Insert
Craig Ringer writes:
> On 05/30/2011 10:29 PM, Mathew Samuel wrote:
>
>> 2011-03-28 10:44:28 UTC3609HINT: Consider increasing the configuration
>> parameter "checkpoint_segments".
>> 2011-03-28 10:44:38 UTC3609LOG: checkpoints are occurring too
>> frequently (10 seconds apart)
>> 2011-03-28 10:
hi all
I am trying to create a second instance of PostgreSQL (8.3) on a
Windows 2003 server with initdb, but am running into an error message
I can't seem to resolve.
Here's what I've done so far:
Created a new local account 'postgres_test' for the 2nd instance to run under.
I stopped the first
On 31/05/2011 16:16, jlhgis wrote:
Create a new data directory for the 2nd instance of Postgres, located
at "E:\SPDB_Files\PostgreSQL_Test\8.3\data" and gave the
'postgres_test' account full control of everything under
\PostgreSQL_Test
[...]
initdb –A md5 –D E:\Spatial_DB_Files\PostgreSQL_Te
On Tue, May 31, 2011 at 9:24 AM, David Johnston wrote:
> From syntax works fine for literals but how would you then get table.column
> values into the function call - where you want to evaluate multiple rows
> from the source table? In order to feed rows to a function you need the
> function in t
I'm doing some tests with date-time related fields to design my web
application.
I was already dissatisfied with Postgresql handling of timezones
concepts (issue
already discussed here - not entirely PG's fault, rather a SQL thing)
and I vehemently
reject the idea of a global server-side timezone
Hello list,
. Postgresql8.3
. mybatis-3.0.5-SNAPSHOT.jar
. mybatis-spring-1.0.1-SNAPSHOT.jar
. spring3.0.5
. postgresql-9.0-801.jdbc4.jar
SqlSession sql_session = sqlSessionFactory.openSession(false);
sql_session.commit();
Always got:
===
### Error committing transactio
See my thoughts below. Other user's opinions (or a pointer to where this
topic has been previously discussed) are greatly welcomed.
> -Original Message-
> From: Merlin Moncure [mailto:mmonc...@gmail.com]
> Sent: Tuesday, May 31, 2011 11:56 AM
> To: David Johnston
> Cc: Tom Lane; pgsql-gen
>
> SqlSession sql_session = sqlSessionFactory.openSession(false);
>
> sql_session.commit();
>
>
We'll presume that you intend (intentionally or otherwise) for auto-commit
to be on since you do not reference any actual JDBC method calls here...
> While for "8.4-702 JDBC 4", the same codes
> -Original Message-
> From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-
> ow...@postgresql.org] On Behalf Of hernan gonzalez
> Sent: Tuesday, May 31, 2011 12:45 PM
> To: pgsql-general@postgresql.org
> Subject: [GENERAL] Some clarification about TIMESTAMP
>
> I vehemently rej
David,
SqlSession sql_session = sqlSessionFactory.openSession(false);
sql_session.commit();
We'll presume that you intend (intentionally or otherwise) for auto-commit
to be on since you do not reference any actual JDBC method calls here...
I'd like always "autocommit = false"
jdbc8.4
> -Original Message-
> From: Emi Lu [mailto:em...@encs.concordia.ca]
> Sent: Tuesday, May 31, 2011 2:06 PM
> To: David Johnston
> Cc: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] "postgresql-9.0-801.jdbc4.jar" always cause
> "org.postgresql.util.PSQLException: Cannot commit when au
hernan gonzalez writes:
> I'm doing some tests with date-time related fields to design my web
> application.
> I was already dissatisfied with Postgresql handling of timezones
> concepts (issue
> already discussed here - not entirely PG's fault, rather a SQL thing)
> and I vehemently
> reject the
> There are any number of
> server-side settings that can affect the interpretation (and display)
> of your data. Datestyle for example already renders this position
> untenable.
What makes me a little uncomfortable in this assertion -and in many
parts of PG docs-
is that emphasis put on what "is
On Tue, May 31, 2011 at 10:45 AM, hernan gonzalez wrote:
> In this scenario, I assumed the natural convention is: store just a
> UTC time, using a TIMESTAMP. I believe that's the idea
> of a plain TIMESTAMP.
No a plain timestamp has no timezone, UTC or otherwise. it's more
like what you'd use if
On Tue, May 31, 2011 at 11:57 AM, David Johnston wrote:
> See my thoughts below. Other user's opinions (or a pointer to where this
> topic has been previously discussed) are greatly welcomed.
> Thank you for the technical detail on how ().* gets expanded by the engine.
> I still believe it would
On 05/31/2011 12:00 PM, hernan gonzalez wrote:
There are any number of
server-side settings that can affect the interpretation (and display)
of your data. Datestyle for example already renders this position
untenable.
What makes me a little uncomfortable in this assertion -and in many
parts
Merlin Moncure writes:
> There have been multiple complaints about this in the archives. In
> the old days, you would have to rewrite your query to use the 'select
> * from func()' form (which isn't always so easy) or use a subquery and
> the 'offset 0' hack. Running in to this problem has actua
Hi, in 8.4 how does the regular expression functions in postgresql handle
special UTF-8 characters?
for example:
SELECT name,substring(name from E'\\w+\\s(\\w+)$') from nodes;
fails to select characters like ü ø æ å
--
Håvard Wahl Kongsgård
http://havard.security-review.net/
Hello,
I hope that I am not wasting your time, I tried to restore a part of a
database
and I faced couple of obstacles. First of all, I tried to restore a certain set
of schemas without restoring a certain relations. I wanted to do that in order
to create some automated dummy data for testing
On Tue, May 31, 2011 at 04:00:21PM -0300, hernan gonzalez wrote:
> frequently (mostly?)
> access the DB remotely and from a client interface (eg. JDBC), one
> would say that the
> display/interpret (from to a string) ocurrs normally in an upper
> layer, not in the DB.
In my experience, FWIW, hand
Hello,
I am interested in creating a system where Java EE distributed
transactions would work with multiple Postgres databases. I'm having
some difficulty understanding the transaction isolation guarantees that
I would get from this configuration. Can I make my distributed
transactions SERI
=?ISO-8859-1?Q?H=E5vard_Wahl_Kongsg=E5rd?=
writes:
> Hi, in 8.4 how does the regular expression functions in postgresql handle
> special UTF-8 characters?
Badly :-(
> for example:
> SELECT name,substring(name from E'\\w+\\s(\\w+)$') from nodes;
> fails to select characters like ü ø æ å
Should
On Tue, May 31, 2011 at 3:28 PM, Tom Lane wrote:
> Merlin Moncure writes:
>> There have been multiple complaints about this in the archives. In
>> the old days, you would have to rewrite your query to use the 'select
>> * from func()' form (which isn't always so easy) or use a subquery and
>> th
Merlin Moncure writes:
> I've never taken the time to really get my head around 'lateral'
> enough to say for sure if it provides clean workarounds for all the
> cases that get people into hot water. The case that used to get me a
> lot is (the unfortunately generally under utilized) custom aggre
On Tue, May 31, 2011 at 5:01 PM, Tom Lane wrote:
> Merlin Moncure writes:
>> I've never taken the time to really get my head around 'lateral'
>> enough to say for sure if it provides clean workarounds for all the
>> cases that get people into hot water. The case that used to get me a
>> lot is (
On 05/31/2011 10:46 PM, Mathew Samuel wrote:
Thanks for your help, here are the results from running that you provided to me:
$ egrep '^[^#[:space:]]' postgresql.conf |cut -d '#' -f 1
[snip]
OK, nothing interesting there. Thanks for posting it, though; I was
wondering if there might be a very
On 05/31/2011 11:16 PM, jlhgis wrote:
I stopped the first instance of PostgreSQL and made a copy of the
‘postgresql’ software installation. Copied
"D:\Database_Apps\PostgreSQL_Dev" to
"D:\Database_Apps\PostgreSQL_Test".
You don't need to do that. It's fine to use the same binaries and just
hav
Leif Jensen wrote:
>
> Thank you for your comment. Yes, it would be nice to get some more
> comments on the allocate/deallocate on a connection issue.
>
> I have verified that in my case deallocating a prepared statement,
> it guesses the wrong connection and returns an error. (The right
> one is
>>The data directory in the initdb command is different
>>from the one you mention above - is that the case or
>>were you just abbreviating?
Yes, I had intended them to be different. My D drive is a small
internal hard drive where I install all my application software, but I
wanted to put the data
On 1/06/2011 4:52 AM, Pete Chown wrote:
Is there a solution to this, or is the point that I'm simply asking too
much? Perhaps the Java EE container is not promising consistency in the
sense I'm talking about.
Distributed transactions will give you atomicity if done right - with
two-phase comm
Hi folks,
I am curious about why the following doesn't work as expected (tested
on 9.0.3 and HEAD).
CREATE OR REPLACE FUNCTION make_schema(_name text)
RETURNS void LANGUAGE plpgsql VOLATILE AS $$
DECLARE
_quoted text;
BEGIN
_quoted = quote_ident(_name);
EXECUTE 'CR
On 31/05/2011 11:16 PM, jlhgis wrote:
initdb –A md5 –D E:\Spatial_DB_Files\PostgreSQL_Test\8.3\data -E
UTF8 –-locale=C -X F:\pgsql_test_logs –U pgsql_test_su –W
Aaaah... your typeface just gave me a clue. It's impossible for me to
tell if the issue above is just your mail client being "
Brendan Jurd writes:
> CREATE OR REPLACE FUNCTION make_schema(_name text)
> RETURNS void LANGUAGE plpgsql VOLATILE AS $$
> DECLARE
> _quoted text;
> BEGIN
> _quoted = quote_ident(_name);
> EXECUTE 'CREATE SCHEMA ' || _quoted;
> EXECUTE 'SET LOCAL search_path
Craig Ringer wrote:
On 1/06/2011 4:52 AM, Pete Chown wrote:
Is there a solution to this, or is the point that I'm simply asking too
much? Perhaps the Java EE container is not promising consistency in the
sense I'm talking about.
Distributed transactions will give you atomicity if done right
On 06/01/2011 11:11 AM, Rob Sargent wrote:
My recollection of distributed transactions is that the manager tells
all players to do their thing. Then they each tell the manager "ok, did
the deed". Then, if all players say ok, each of them is told by the
manager to go ahead and commit, else rollba
On 1 June 2011 13:08, Tom Lane wrote:
> Brendan Jurd writes:
>> It seems that the first call to make_schema succeeds, but the second
>> fails when it gets to the INSERT. The duplicate key complaint seems
>> to suggest that the INSERT statement is resolving t as a.t, instead of
>> the newly creat
Hi,
I am trying to use psql \set and \echo commands to set some internal
variables.
My variable starts with single quote and ends with single quote.
That is actual value of the variable.
Eg.
set cur_db 'pgdb'
\echo :cur_db
--I am expecting here 'pgdb' but psql shows pgdb
As mentioned above, I am
Hi,
I am trying to use psql \set and \echo commands to set some internal
variables.
My variable starts with single quote and ends with single quote.
That is actual value of the variable.
Eg.
set cur_db 'pgdb'
\echo :cur_db
--I am expecting here 'pgdb' but psql shows pgdb
As mentioned above, I am
50 matches
Mail list logo
