On Thu, Dec 27, 2012 at 5:39 PM, Peter Bex peter@xs4all.nl wrote:
On Thu, Dec 27, 2012 at 12:31:08PM -0300, Claudio Freire wrote:
On Thu, Dec 27, 2012 at 11:46 AM, Peter Bex peter@xs4all.nl wrote:
Implementing a more secure challenge-response based algorithm means
a change in the
Hi Karl,
Sorry for the slow reply ...
Excerpt from Karl O. Pinc k...@meme.com On Mon, Dec 10, 2012 at 5:00 AM:
I was thinking along the same lines, that case 2) stderr to a file
or pipe needs addressing. I think it's necessary to address the
issue now. Otherwise we risk cluttering up the
Hi Karl,
I have given the patch a quick review and read the related mails
following its initial submission.
I agree with that functionality along these lines is desirable. The
ability to manage output from within psql at least as richly as is
possible with shell redirection - and change it
Patch for the changes discussed in
http://archives.postgresql.org/pgsql-hackers/2010-10/msg00919.php
attached (eventually ...)
In summary: If the input file (-f) doesn't exist or the ouput or log
files (-o and -l) can't be created psql exits before prompting for a
password.
Regards,
Alastair.
On Thu, May 31, 2012 at 9:11 PM, Magnus Hagander mag...@hagander.net wrote:
On Thu, May 31, 2012 at 9:04 PM, Bruce Momjian br...@momjian.us wrote:
On startup, psql shows the SSL information:
$ psql 'sslmode=require host=localhost'
psql (9.2beta1)
SSL connection (cipher:
Excerpts from Kohei KaiGai kai...@kaigai.gr.jp wrote on Fri, May 25,
2012 at 11:08 PM:
If we assume RLS is applied when user has
no privileges on tables, the current ExecCheckRTEPerms()
always raises an error towards unprivileged users, prior to
execution of queries.
Isn't it preferable
On Wed, May 23, 2012 at 5:09 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Kohei KaiGai kai...@kaigai.gr.jp writes:
Let me have a discussion to get preferable interface for row-level security.
My planned feature will perform to append additional conditions to WHERE
clause implicitly, to restrict
On Fri, Apr 29, 2011 at 8:11 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Greg Stark gsst...@mit.edu writes:
On Fri, Apr 29, 2011 at 5:45 PM, Christopher Browne cbbro...@gmail.com
wrote:
The bike shedding that I'd rather have would involve enclosing
prompts with /* comments */ so that cut'n'paste
On Thu, Apr 7, 2011 at 6:49 AM, Andrew Dunstan and...@dunslane.net wrote:
On 04/07/2011 12:29 AM, Tom Lane wrote:
Robert Haasrobertmh...@gmail.com writes:
On Wed, Apr 6, 2011 at 7:54 PM, Stephen Frostsfr...@snowman.net wrote:
* Andrew Dunstan (and...@dunslane.net) wrote:
The surprising
On Tue, Nov 30, 2010 at 9:24 PM, Marko Tiikkaja
marko.tiikk...@cs.helsinki.fi wrote:
On 11/30/2010 02:12 PM, Kevin Grittner wrote:
Daniel Loureirodan...@termasa.com.br wrote:
to me the key its security - its a anti-DBA-with-lack-of-attention
feature.
Well, it seems pretty weak to me for
Hi
I am a keen Postgres user and I run my local PUG (JNBPUG in Gauteng,
South Africa), but I have found the idea of contributing on a code
level daunting.
Having read the many warnings along the lines of It's still on the
todo because it isn't trivial I have identified what I believe is a
On Thu, Oct 14, 2010 at 4:05 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Alastair Turner b...@ctrlf5.co.za writes:
I am proposing altering psql to raise certain errors and exit before
prompting for a password. These errors would have to be on items which
didn't leak any information, my current list
Excerpt from Hitoshi Harada umi.tan...@gmail.com - Thu, Oct 14, 2010
at 4:32 PM:
Just for information, did you pick this topic from TODO
list? If so, could you attach links to the entry or to some related
former thread? And in general it is encouraged that you'd better send
one feature per a
A suggestion, based on what I believe would be ideal default settings
for a fully developed SR capability. The thought being that as long as
the default behaviour was stable additional knobs could be added
across version boundaries without causing trouble.
Per slave the master needs to know:
-
On Tue, May 25, 2010 at 6:28 PM, Simon Riggs si...@2ndquadrant.com wrote:
...
The best parameter we can specify is the number of servers that we wish
to wait for confirmation from. That is a definition that easily manages
the complexity of having various servers up/down at any one time. It
2010/3/5 François Pérou francois.pe...@free.fr:
Thanks for your answers.
To speak frankly:
* I wrote the Drupal guide for porting from MySQL to PostgreSQL.
* I am also the author of remarks about people should use PostgreSQL to
write portable SQL.
* I am very surprised by the SQL level
On Tue, Jan 26, 2010 at 1:08 PM, David E. Wheeler da...@kineticode.com wrote:
.
Because it's an aggregate that cocatenates values. It's not an aggregate
that lists things. I also like concat_agg better than string_agg because
it's not limited to acting on strings.
.
Given that it
On Tue, Jan 26, 2010 at 1:23 PM, Alastair Turner b...@ctrlf5.co.za wrote:
.
Given that it potentially produces a delimited list, not a straight
conacatenation (and that list is unacceptable since it would be
descriptive as a noun but not as a verb) would implode_agg not be the
most
18 matches
Mail list logo
