On 03/18/2013 12:07 AM, Craig Ringer wrote:
So this problem is verified.
Thanks for taking the time to look into this. Good to know I'm not
crazy.
What we need to happen instead is for root.crt to contain only the
trusted certificates and have a *separate* file or directory for
intermediate
On 03/18/2013 01:07 PM, Craig Ringer wrote:
System wide installation of the root may allow OpenSSL to discover it
and use it for verification back to the root without having to trust it
to sign clients. I'll do some more checking to see if this is possible
with how Pg uses OpenSSL but I'm
On 03/18/2013 02:27 PM, Ian Pilcher wrote:
On 03/18/2013 12:07 AM, Craig Ringer wrote:
So this problem is verified.
* Trusted certificates - What currently goes in the (unfortunately
named) root.crt file.
Well, a little unfortunate. It contains roots of *client authentication*
trust, which
Thanks. Case-folding was my problem.
Is there any way of getting PostgreSQL to work according to the SQL standard
(The folding of
unquoted names to lower case in PostgreSQL is incompatible with the SQL
standard, which says that unquoted names should be folded to
upper case.), so
Thanks. Case-folding was my problem.
Is there any way of getting PostgreSQL to work according to the SQL standard
(The folding of
unquoted names to lower case in PostgreSQL is incompatible with the SQL
standard, which says that unquoted names should be folded to
upper case.), so
Charl Roux wrote:
Is there any way of getting PostgreSQL to work according to the SQL standard
(The folding of unquoted
names to lower case in PostgreSQL is incompatible with the SQL standard,
which says that unquoted
names should be folded to upper case.), so there is no need for me to add
On 17 Mar 2013, at 04:30, Tom Lane t...@sss.pgh.pa.us wrote:
Oleg Alexeev oalex...@gmail.com writes:
* it is varchar columns, 256 and 32 symbols length
* encoding, collation and ctype: UTF8, en_US.utf8, en_US.utf8
* autovacuum, fsync off, full_page_writes = on, wal_writer_delay = 500ms,
Craig, all,
* Craig Ringer (cr...@2ndquadrant.com) wrote:
PROBLEM VERIFIED
Let me just say ugh. I've long wondered why we have things set up in
such a way that the whole chain has to be in one file, but it didn't
occur to me that it'd actually end up causing this issue. In some ways,
I really
On 03/18/2013 03:25 AM, Charl Roux wrote:
Thanks. Case-folding was my problem.
Is there any way of getting PostgreSQL to work according to the SQL
standard (The folding of unquoted names to lower case in PostgreSQL is
incompatible with the SQL standard, which says that unquoted names
should be
On Thu, Mar 14, 2013 at 1:55 PM, prashantmalik prashantmal...@gmail.com wrote:
Hello,
We are facing very HIGH memory utilization on postgreSQL server and need
help.
Total RAM : 32GB
Total CPU : 16cores
Merlin Moncure wrote:
problem is psql buffering whole result set in memory before outputting
result. note this is core problem with libpq client library until
very recently. there are several easy workarounds:
*) use cursor
*) don't select entire table, page it out using index
I have a table that I want to use as a queue with all functionality (Insert,
update, delete) embodied in a stored procedure. Inserts and deletes are no
problem. An external program would call the stored procedure to get one or
more emails to work on, selecting on state='N', then updating the row
In prepping for an upgrade to 9.2.3, I stumbled across this:
CREATE TABLE foo
(
myint integer,
string1 text,
string2 text
)
WITH (
OIDS=FALSE
);
insert into foo values (12345,'Y','N');
select * from foo f where f.myint = 12345 or f.name='Y'
In 9.2.3, this returns:
ERROR: column
On Mar 18, 2013, at 9:49 AM, Jeff Amiel becauseimj...@yahoo.com wrote:
In prepping for an upgrade to 9.2.3, I stumbled across this:
CREATE TABLE foo
(
myint integer,
string1 text,
string2 text
)
WITH (
OIDS=FALSE
);
insert into foo values (12345,'Y','N');
select * from
Jeff Amiel becauseimj...@yahoo.com writes:
select * from foo f where f.myint = 12345 or f.name='Y'
In 9.2.3, this returns:
ERROR: column f.name does not exist
LINE 1: select * from foo f where myint = 12345 or f.name='Y'
in 8.4.6 ,this returns no error (and gives me the row from the
On our 9.0.4[1] server my regexp_replace is a no-op, but on the 9.0.3[2]
test machine and my 9.1.2[3] dev box all is fine
This is may statement
update cms.segment_data s
set text = regexp_replace(s.text,
'(^.*)ns/acres/pathology/dx/1.5(.*$)',
E'\\1ns/acres/pathology/dx/1.6\\2')
from
Rob Sargent robjsarg...@gmail.com writes:
On our 9.0.4[1] server my regexp_replace is a no-op, but on the 9.0.3[2]
test machine and my 9.1.2[3] dev box all is fine
AFAICS from the commit logs, there were no changes affecting the regex
code between 9.0.3 and 9.0.4. I'm suspicious that your
On 17 March 2013 08:30, Tom Lane t...@sss.pgh.pa.us wrote:
Oleg Alexeev oalex...@gmail.com writes:
* it is varchar columns, 256 and 32 symbols length
* encoding, collation and ctype: UTF8, en_US.utf8, en_US.utf8
* autovacuum, fsync off, full_page_writes = on, wal_writer_delay = 500ms,
On 03/18/2013 01:19 PM, Tom Lane wrote:
Rob Sargent robjsarg...@gmail.com writes:
On our 9.0.4[1] server my regexp_replace is a no-op, but on the 9.0.3[2]
test machine and my 9.1.2[3] dev box all is fine
AFAICS from the commit logs, there were no changes affecting the regex
code between 9.0.3
Rob Sargent robjsarg...@gmail.com writes:
On 03/18/2013 01:19 PM, Tom Lane wrote:
Rob Sargent robjsarg...@gmail.com writes:
On our 9.0.4[1] server my regexp_replace is a no-op, but on the 9.0.3[2]
test machine and my 9.1.2[3] dev box all is fine
AFAICS from the commit logs, there were no
On 03/18/2013 02:01 AM, Craig Ringer wrote:
This appears to match Ian's description of having a validation-only cert
list and a separate list of certs used to verify clients. I'd like to
follow Apache's model:
Ready for some more good news?
It's possible that I'm missing something, but Apache
On 03/18/2013 02:40 PM, Tom Lane wrote:
Rob Sargent robjsarg...@gmail.com writes:
On 03/18/2013 01:19 PM, Tom Lane wrote:
Rob Sargent robjsarg...@gmail.com writes:
On our 9.0.4[1] server my regexp_replace is a no-op, but on the 9.0.3[2]
test machine and my 9.1.2[3] dev box all is fine
Hi guys,
What is the road map for Postgres on the AIX platform? I understand that
the pg build farm contains an AIX 5.3 server; are there any plans to
upgrade to 6.1 and 7.1?
Our servers run on AIX and we are evaluating using Postgres as the RDBMS.
Part of my evaluation is understanding where the
Shaun Thomas stho...@optionshouse.com wrote:
On 03/15/2013 08:36 AM, Kevin Grittner wrote:
I occasionally hear someone maintaining that having a meaningless
sequential ID column as the primary key of each table is required
by the relational model.
You know, I've heard you mention this a
On 3/18/2013 3:39 PM, Wasim Arif wrote:
What is the road map for Postgres on the AIX platform? I understand
that the pg build farm contains an AIX 5.3 server; are there any plans
to upgrade to 6.1 and 7.1?
Our servers run on AIX and we are evaluating using Postgres as the
RDBMS. Part of my
The Surge 2013 CFP is open. For details or to submit a paper, please visit
http://surge.omniti.com/2013
--
Katherine Jeschke
Director of Marketing and Creative Services
OmniTI Computer Consulting, Inc.
11830 West Market Place, Suite F
Fulton, MD 20759
O: 240-646-0770, 222
F: 301-497-2001
C:
Are is the contents of the .backup file (generated by pg_stop_backup())
documented anywhere? (Some of it is self-explanatory, of course). If not, is
there a quick summary of what START WAL LOCATION, STOP WAL LOCATION, and
CHECKPOINT LOCATION are?
--
-- Christophe Pettus
x...@thebuild.com
Tom,
Thank you for your prompt reply. Your advice has pointed me in the right
direction.
I now have the wrapper identifying columns that are inputs to the web service,
and thus parameterisable. The ec_classes, left_join_clauses and
right_join_clauses trees are scanned for Var exprs that match
Wasim Arif wasima...@gmail.com writes:
What is the road map for Postgres on the AIX platform? I understand that
the pg build farm contains an AIX 5.3 server; are there any plans to
upgrade to 6.1 and 7.1?
The reason there's an AIX 5.3 buildfarm member is that someone cares
enough about
Adam Zegelin a...@relational.io writes:
My path generation logic seems to work:
baserel-cheapest_parameterized_paths = (
{FOREIGNPATH
:pathtype 120
:parent_relids (b 3)
:required_outer (b 1 2)
:rows 500
:startup_cost 0.00
:total_cost 0.00
:pathkeys
On Mar 16, 2013, at 8:30 AM, Jason Dusek jason.du...@gmail.com wrote:
However, it is not clear to me at this juncture how to get the
return type for a statement, given its text. Preparing and
looking it up in pg_prepared_statements will retrieve the
argument types but not the return type.
On Mar 18, 2013, at 7:36 PM, Christophe Pettus wrote:
Are is the contents of the .backup file (generated by pg_stop_backup())
documented anywhere? (Some of it is self-explanatory, of course). If not,
is there a quick summary of what START WAL LOCATION, STOP WAL LOCATION, and
CHECKPOINT
Maybe we're barking up the wrong tree by suspecting the regex itself.
Perhaps the updates were suppressed by a trigger, or the transaction
rolled back instead of committing, or some such?
regards, tom lane
Barking mad, more like it. I had rolled back the execution of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/18/2013 08:55 PM, Stephen Frost wrote:
Makes sense to me. I'm not particular about the names, but isn't this
set of CAs generally considered intermediary? Eg: 'trusted', '
intermediate', etc?
They are intermediary, but we're dealing with the
Craig,
* Craig Ringer (cr...@2ndquadrant.com) wrote:
They are intermediary, but we're dealing with the case where trust and
authorization are not the same thing. Trust stems from the trusted root
in the SSL CA model, but that's a chain of trust for *identity*
(authentication), not
35 matches
Mail list logo
