in many other places in the source as well, but
it's certainly fairly ugly. So I see nothing wrong cleaning it up whe
nspotted.
Thus, patch applied, thanks!
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers
On Mon, Sep 3, 2012 at 6:11 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
On Wed, Aug 22, 2012 at 11:58 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Make a cut at a major-features list for 9.2.
This is open to debate of course, but it's past time we had
On Fri, Aug 31, 2012 at 2:05 PM, Magnus Hagander mag...@hagander.net wrote:
On Aug 28, 2012 9:59 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
On Tue, Aug 28, 2012 at 6:42 PM, Tom Lane t...@sss.pgh.pa.us wrote:
I don't see anything particularly
On Tue, Sep 4, 2012 at 3:51 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
On Aug 28, 2012 9:59 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Well, why don't we just s/restoring/processing/ in the debug message,
and call it good?
Are we allowed to backpatch
in pgpipe() before.. It was
removed in d2c1740dc275543a46721ed254ba3623f63d2204, but that's
because it was dead at the time. Do we need to bring it back?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers
.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
it is.
But I think we should add the (closely related) base backups from
slave to the list as well - I've had more people say they're really
going to use that one than the cascading replication. Perhaps add them
both on the same bullet point?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http
that our kill
emulation only worked within the backend environment, but of course
pg_ctl wouldn't work if that were so. So this is easier than I thought.
Yeah, kill works fine from non-backend as long as the *receiver* has
our backend environment.
--
Magnus Hagander
Me: http
On Mon, Sep 3, 2012 at 8:51 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
On Mon, Sep 3, 2012 at 7:07 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Hmm, after looking at src/port/kill.c it doesn't seem like there's much
of a problem with doing that. I had had
think it should be reduced to warning when connected to a newer
server.
Seems like a good idea to me. +1. (Obviously keeping the first line
that shows that the version numbers are different, but not WARNING)
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com
On Aug 28, 2012 9:59 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
On Tue, Aug 28, 2012 at 6:42 PM, Tom Lane t...@sss.pgh.pa.us wrote:
I don't see anything particularly incorrect about that. The point of
the --verbose switch is to track what pg_dump
...
We also get the buildfarms functionality for collecting logs and
reporting them. Just some more we don't have to build a new set of
scripts for.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers
the functions to
tell them if they're restoring or not?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
On Tue, Aug 28, 2012 at 6:42 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
but in plaintext:
$ pg_dump -v postgres -Fp -t t /dev/null
pg_dump: creating TABLE t
pg_dump: restoring data for table t
pg_dump: dumping contents of table t
pg_dump: setting
fragile and very environment-dependent. I'd rather not upset it
this close to release - especially not after RC wrap.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
there's some logic in that, it's not documented
AFAICT. Or am I just not finding the docs?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
On Wed, Aug 15, 2012 at 5:39 PM, Bruce Momjian br...@momjian.us wrote:
On Mon, Aug 15, 2011 at 01:03:35PM +0200, Magnus Hagander wrote:
The pg_stat_replication view exposes all the fields in
StandbyReplyMessage *except* for the timestamp when the message was
generated. On an active system
of work, let's do that later instead to get the feature
in? If the second, does anyone have plans to fix it? It is a quite
annoying limitation :(
That said, this functionality would be useful even *if* the enum label
addition was made transactional...
--
Magnus Hagander
Me: http
On Thu, Aug 23, 2012 at 1:35 PM, Andrew Dunstan and...@dunslane.net wrote:
On 08/23/2012 06:47 AM, Magnus Hagander wrote:
On Mon, Aug 20, 2012 at 4:52 PM, Andrew Dunstan and...@dunslane.net
wrote:
Here is a patch for this feature, which should alleviate some of the woes
caused by adding
On Thu, Aug 23, 2012 at 3:42 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
postgres=# select to_timestamp('2012-08-01', '-mm-dd');
to_timestamp
2012-08-01 00:00:00+02
postgres=# select to_timestamp('2012-08-00', '
that the client-side code plays along.
That sounds like a good idea for other reasons as well - manual
connections attempting to get in during an upgrade will just fail with
a no connection error, which makes sense...
So, +1.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill
On Thu, Aug 9, 2012 at 4:17 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
The check in PostmasterMain():
if (ReservedBackends = MaxBackends)
{
write_stderr(%s: superuser_reserved_connections must be less
than
max_connections\n
the relation to
max_connections, which it really should. And it should probably be
enforced the same way that superuser_reserved_connections is, so you
can't set it to silly high values.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql
somehow try to keep track of those that
*are* linked from the documentation. I assume you just grep:ed this
time, or something like that? Perhaps we should assign all such pages
a specific category or so on the wiki, so we can police them a bit
extra hard?
--
Magnus Hagander
Me: http
disregard
my last one.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
to the documentation.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
or the corresponding one in the old pgweb repo). That can probably be
adapted to be put in the new one - seems it was genereally just
removed because there was no beta available, and the intentino wasn't
that the page should remain useless once a beta was out..
--
Magnus Hagander
Me: http://www.hagander.net
of the existing rough edges.
That would be the serious engineering time Robert is referring to,
no? If you knew how to do it already it wouldn't require serious
engineering time, just SMOP.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql
Should we consider if we can make pg_ctl -w work for promote as well?
The main problem is, I guess, that it can't log in - so wed' need
something like PQping() that actually checked if it was master or
slave?
//Magnus
-- Forwarded message --
From: Manoj Govindassamy ma
patch lying around that implemented this as a libpq
connection option. It was just a quick hack to work around a situation
just like this (though not for replication), and ISTM that's the
proper place to put it.
I'll stick it on my TODO to try to clean that one up and submit for 9.3..
--
Magnus
On Tue, Jul 31, 2012 at 5:06 PM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
Excerpts from Magnus Hagander's message of jue jul 12 07:35:11 -0400 2012:
On Tue, Jul 10, 2012 at 6:45 PM, Fujii Masao masao.fu...@gmail.com wrote:
When an error happens after replication connection has been
,
if this is not in the Open Items list, please put it there so that we
don't forget it before the 9.2 release.
Yep, done.
And I'll go take it off :-)
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
no choice. I'm not sure about Mac, but AFAIK certainly the ones
downloading the binaries will get our set of TZ files. That
represents a very non-trival portion of our users.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list
On Mon, Jun 25, 2012 at 2:26 PM, Magnus Hagander mag...@hagander.net wrote:
On Mon, Jun 25, 2012 at 4:04 AM, Robert Haas robertmh...@gmail.com wrote:
On Fri, Jun 22, 2012 at 12:38 PM, Euler Taveira eu...@timbira.com wrote:
On 20-06-2012 17:40, Marko Kreen wrote:
On Wed, Jun 20, 2012 at 10:05
On Thu, Jul 12, 2012 at 11:41 AM, Bernd Helmle maili...@oopsware.de wrote:
Do we have a schedule for when next back-branch releases are packaged (i hope
i
didn't miss any announcement...)?
No, there is no such schedule (yet).
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http
On Tue, Jul 10, 2012 at 6:45 PM, Fujii Masao masao.fu...@gmail.com wrote:
On Tue, Jul 10, 2012 at 6:27 AM, Magnus Hagander mag...@hagander.net wrote:
On Mon, Jul 9, 2012 at 8:23 PM, Fujii Masao masao.fu...@gmail.com wrote:
Hi,
I found several problems in pg_receivexlog, e.g., memory leaks
failure? Shouldn't that end up under the
could not read copy data branch, which already returns false?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
On Thu, Jul 12, 2012 at 6:07 PM, Fujii Masao masao.fu...@gmail.com wrote:
On Thu, Jul 12, 2012 at 8:39 PM, Magnus Hagander mag...@hagander.net wrote:
On Tue, Jul 10, 2012 at 7:03 PM, Fujii Masao masao.fu...@gmail.com wrote:
On Tue, Jul 10, 2012 at 3:23 AM, Fujii Masao masao.fu...@gmail.com
between sync and async just fine on a live
system. And you can control that from some external monitor to define
your own rules for exactly when it should drop to async mode.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing
-- opinions?
Definitely seems like a bug to me, yes.
And while I haven't verified that the suggested fix actually fixes it
for me, it sounds reasonable :)
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers
).
What's the actual usecase for promoting the slave, upgrading it and
then *not* using it, which is what I think this paragraph suggests?
And I think the sentence about running rsync is extremely vague - run
rsync where and how? What are you actually trying to suggest people
do?
--
Magnus Hagander
Me
On Tue, Jul 10, 2012 at 6:26 PM, Bruce Momjian br...@momjian.us wrote:
On Tue, Jul 10, 2012 at 06:21:35PM +0200, Magnus Hagander wrote:
On Tue, Jul 10, 2012 at 6:17 PM, Bruce Momjian br...@momjian.us wrote:
On Tue, Jul 10, 2012 at 12:04:50PM -0400, Tom Lane wrote:
Bruce Momjian br
On Tue, Jul 10, 2012 at 6:59 PM, Bruce Momjian br...@momjian.us wrote:
On Tue, Jul 10, 2012 at 06:29:24PM +0200, Magnus Hagander wrote:
Testing maybe? I feel we have just avoided saying what you can and
can't do with the standbys and pg_upgrade, so I think we have to state
something
On Tue, Jul 10, 2012 at 7:27 PM, Bruce Momjian br...@momjian.us wrote:
On Tue, Jul 10, 2012 at 07:06:39PM +0200, Magnus Hagander wrote:
rsync where and how? What are you actually trying to suggest people
do?
Updated docs attached.
I suggest just removing the rsync part completely
will.
I'm not sure. The only character that's certainly an issue is /. Are
there any others on file systems that we want to support?
\ and : if we care at all about windows
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing
explaining exactly what they are, so we don't have to
reverse-engineer the patch to figure that out?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
of that
capability.
I feel we have to be honest in what our current development process does
poorly.
+1.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
On Sat, Jul 7, 2012 at 12:48 PM, Martijn van Oosterhout
klep...@svana.org wrote:
On Sat, Jul 07, 2012 at 11:36:41AM +0200, Magnus Hagander wrote:
I've never thought of it in terms of friction, but I think that term
makes a lot of sense. And it sums up pretty much one of the things
that I find
many WAL buffers are needed. This patch
seems like it's on the right track, at least telling you how often you're
running out.
We could keep a high watermark of what's the largest percentage we've
used, perhaps?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill
On Sat, Jul 7, 2012 at 4:42 PM, Bruce Momjian br...@momjian.us wrote:
On Sat, Jul 07, 2012 at 12:59:02PM +0200, Magnus Hagander wrote:
On Sat, Jul 7, 2012 at 12:48 PM, Martijn van Oosterhout
klep...@svana.org wrote:
On Sat, Jul 07, 2012 at 11:36:41AM +0200, Magnus Hagander wrote:
I've never
On Sat, Jul 7, 2012 at 4:48 PM, Bruce Momjian br...@momjian.us wrote:
On Sat, Jul 07, 2012 at 04:45:42PM +0200, Magnus Hagander wrote:
That's not to say it's a horrible idea, it's just to say that things
are never as easy as they first look.
BTW, the *bigger* issue with this path
On Sat, Jul 7, 2012 at 7:06 PM, Robert Haas robertmh...@gmail.com wrote:
On Jul 7, 2012, at 8:54 AM, Magnus Hagander mag...@hagander.net wrote:
On Sat, Jul 7, 2012 at 3:52 PM, Robert Haas robertmh...@gmail.com wrote:
On Jul 7, 2012, at 9:07 AM, Euler Taveira eu...@timbira.com wrote:
On 07-07
* I renamed the macro to COMPLETE_WITH_FUNCTION_ARG - to make it even
more clear what it does
Thanks!
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
On Wed, Jul 4, 2012 at 4:21 PM, David E. Wheeler da...@justatheory.com wrote:
On Jul 4, 2012, at 9:15 AM, Magnus Hagander wrote:
Not really. We have nowhere else to recommend, since we don't run a
replacement for it. And we really don't want to get involved in
listing all the different third
On Tue, Jul 3, 2012 at 10:32 PM, Dave Page dp...@pgadmin.org wrote:
On Tuesday, July 3, 2012, Peter Geoghegan wrote:
On 3 July 2012 20:20, Magnus Hagander mag...@hagander.net wrote:
The second one removes the reference to pgfoundry completely. As a
step in the deprecation.
I'd prefer
On Tue, Jul 3, 2012 at 10:01 PM, David E. Wheeler da...@justatheory.com wrote:
On Jul 3, 2012, at 9:20 PM, Magnus Hagander wrote:
The smaller one, pgfoundry_1.diff, removes the suggestion to apply for
new projects on pgfoundry. The reason for this being that pgfoundry
doesn't *accept* new
On Tue, Jul 3, 2012 at 9:58 PM, Bjorn Munch bjorn.mu...@oracle.com wrote:
On 03/07 21.24, Magnus Hagander wrote:
Our documentation still refers to PostgreSQL bundled in solaris, and
references downloads to the pgfoundry project.
Oh! I wasn't aware of that.
Attached patch removes all those
On Wed, Jul 4, 2012 at 9:18 AM, Albe Laurenz laurenz.a...@wien.gv.at wrote:
Magnus Hagander wrote:
Attached are two patches, one of which I'd like to apply. Open for
discussion on which one.
The smaller one, pgfoundry_1.diff, removes the suggestion to apply for
new projects on pgfoundry
On Mon, Jul 2, 2012 at 8:17 PM, Fujii Masao masao.fu...@gmail.com wrote:
On Mon, Jul 2, 2012 at 4:01 AM, Magnus Hagander mag...@hagander.net wrote:
On Sun, Jul 1, 2012 at 7:14 PM, Fujii Masao masao.fu...@gmail.com wrote:
On Fri, Jun 29, 2012 at 7:22 PM, Magnus Hagander mag...@hagander.net
On Mon, Jun 11, 2012 at 5:24 PM, Fujii Masao masao.fu...@gmail.com wrote:
On Mon, Jun 11, 2012 at 10:04 PM, Magnus Hagander mag...@hagander.net wrote:
On Sun, Jun 10, 2012 at 4:02 PM, Fujii Masao masao.fu...@gmail.com wrote:
On Sun, Jun 10, 2012 at 7:55 PM, Magnus Hagander mag...@hagander.net
of those.
And unfortunately the function we use to load the store seems to be
undocumented, so it's hard to know what we're supposed to use..
(I do agree we should try to figure out a better error message, of course..)
//Magnus
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http
not something for 9.2...
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
to remove or a feature to expand on :O Not sure I'd trust that
to stick around...
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
the reference to pgfoundry completely. As a
step in the deprecation.
I'd prefer to apply the second one, but will settle for the first one
if people object ;)
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
pgfoundry_1.diff
Description: Binary data
all those references completely, since Solaris
packages are now downloaded the same way as other binaries. It leaves
all the notes about how to compile on solaris and other platform
details, of course.
Any objections?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill
potential connection
parameters?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Sun, Jul 1, 2012 at 7:14 PM, Fujii Masao masao.fu...@gmail.com wrote:
On Fri, Jun 29, 2012 at 7:22 PM, Magnus Hagander mag...@hagander.net wrote:
On Wed, Jun 27, 2012 at 7:24 PM, Fujii Masao masao.fu...@gmail.com wrote:
On Thu, Jun 21, 2012 at 3:18 AM, Robert Haas robertmh...@gmail.com
the name from synchronous_standby_names if
you don't like it?
I believe that's just fallout -the main point is that we don't want to
become a sync standby when synchronous_standby_names is set to '*'.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com
On Wed, Jun 27, 2012 at 7:24 PM, Fujii Masao masao.fu...@gmail.com wrote:
On Thu, Jun 21, 2012 at 3:18 AM, Robert Haas robertmh...@gmail.com wrote:
On Wed, Jun 20, 2012 at 7:18 AM, Magnus Hagander mag...@hagander.net wrote:
You agreed to add something like NOSYNC option into START_REPLICATION
On Wed, Jun 27, 2012 at 4:27 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
On Wed, Jun 27, 2012 at 4:14 PM, Tom Lane t...@sss.pgh.pa.us wrote:
cases where people are modifying the wrong hba file. Can we show
the source text of the hba line?
We don't
where the
flags are accepted but fail to produce the correct behavior. I'm
inclined to think this is over-engineering in the absence of evidence
that there are platforms that work this way.
Could we actually turn *that* into a configure test, or will that be
too complex?
--
Magnus Hagander
is superfluous anyhow. Perhaps there is a better
wording for the time being that doesn't implicate the existence or
non-existence of the PID?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers
- does that fail quickly?
Is that not something we might want to do *anyway*?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
On Thu, Jun 28, 2012 at 7:27 PM, Andres Freund and...@2ndquadrant.com wrote:
On Thursday, June 28, 2012 07:19:46 PM Magnus Hagander wrote:
On Thu, Jun 28, 2012 at 7:15 PM, Robert Haas robertmh...@gmail.com wrote:
On Thu, Jun 28, 2012 at 12:13 PM, Thom Brown t...@linux.com wrote:
On 64-bit
looking at is e.g.
http://msdn.microsoft.com/en-us/library/windows/desktop/aa365203(v=vs.85).aspx
- but there are probably others as well if that one doesn't do)
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql
this into 9.2. It doesn't involve
a catalog change, and would make the behavior consistent between the
two releases, instead of changing in 9.1 and then changing again in
9.2. Thoughts?
+1.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql
, but that seems like a bad idea. Or we
could make a separate ereport(LOG) before send it to the client,
perhaps?
Thoughts?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
hba_line.patch
Description: Binary data
--
Sent via pgsql-hackers mailing list
On Wed, Jun 27, 2012 at 3:55 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
When debugging strange and complex pg_hba lines, it can often be quite
useful to know which line is matching a particular connection that
failed for some reason. Because more often
On Wed, Jun 27, 2012 at 3:40 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
On Wed, Jun 27, 2012 at 3:50 AM, Tom Lane t...@sss.pgh.pa.us wrote:
I wonder whether this design can be adapted to Windows? IIRC we do
not have a bulletproof data directory lock
On Wed, Jun 27, 2012 at 4:14 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
On Wed, Jun 27, 2012 at 3:55 PM, Tom Lane t...@sss.pgh.pa.us wrote:
BTW, are you sure that auth_failed is only called in cases where
an hba line has already been identified? Even
interface for
accessing GUCs in psql would help in making it easier, but do we
really need a whole new variable concept?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
On Tue, Jun 26, 2012 at 9:50 AM, Pavel Stehule pavel.steh...@gmail.com wrote:
2012/6/26 Magnus Hagander mag...@hagander.net:
On Tue, Jun 26, 2012 at 7:06 AM, Pavel Stehule pavel.steh...@gmail.com
wrote:
Hello
I worked on simple patch, that enable access from server side to
client side data
will be recreated by
WAL recovery - or is there something else tha tmight be of risk of
similar treatment?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
a warning is also
questionable here.)
can't commend on that part without more investigation.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
as fast as OpenSSL... that'd be pretty compelling.
Or that it takes less code/generates cleaner code...
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
couldn't deal with, because they simply can't know the
future...
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
On Wed, Jun 20, 2012 at 5:20 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Peter Eisentraut pete...@gmx.net writes:
On ons, 2012-06-20 at 13:26 +0200, Magnus Hagander wrote:
That might actually be a good idea. We can't really change the way we
named the betas, but it's not too late to consider naming
On Wed, Jun 20, 2012 at 1:35 PM, Dickson S. Guedes lis...@guedesoft.net wrote:
2012/6/20 Magnus Hagander mag...@hagander.net:
On Wed, Jun 20, 2012 at 11:23 AM, Marti Raudsepp ma...@juffo.org wrote:
On Wed, Jun 20, 2012 at 12:18 PM, Magnus Hagander mag...@hagander.net
wrote:
(I do believe
. But likely not enough much
better to be inconsistent with previous versions)
For beta2, the only reason was to keep it consistent with beta1.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
On Mon, Jun 11, 2012 at 6:06 PM, Fujii Masao masao.fu...@gmail.com wrote:
On Tue, Jun 12, 2012 at 12:47 AM, Magnus Hagander mag...@hagander.net wrote:
On Mon, Jun 11, 2012 at 5:37 PM, Fujii Masao masao.fu...@gmail.com wrote:
On Mon, Jun 11, 2012 at 3:24 AM, Magnus Hagander mag...@hagander.net
at breaking it, and we are especially concerned
about something like pg_receivexlog... Is it something we could/should
change in the protocl *now* for 9.2, to make it non-broken in any
released version? As in, can we extract just the protocol change and
backpatch that to 9.2beta?
--
Magnus
On Wed, Jun 20, 2012 at 11:23 AM, Marti Raudsepp ma...@juffo.org wrote:
On Wed, Jun 20, 2012 at 12:18 PM, Magnus Hagander mag...@hagander.net wrote:
(I do believe that using the v9.2.0beta marker is
*better*, because then it sorts properly. But likely not enough much
better to be inconsistent
of these ideas is that the configure
list is not a list of exact cipher names, as per Magnus' comment that
the current default includes tests like !aNULL. I am not sure that
we know how to evaluate such conditions if we are applying an
after-the-fact check on the selected cipher. Does OpenSSL expose
On Sat, Jun 16, 2012 at 11:15 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
On Sat, Jun 16, 2012 at 12:55 PM, Tom Lane t...@sss.pgh.pa.us wrote:
It's not obvious to me that we actually *need* anything except the
ability to recognize that a null-encrypted
On Sun, Jun 17, 2012 at 12:13 AM, Dimitri Fontaine
dimi...@2ndquadrant.fr wrote:
Magnus Hagander mag...@hagander.net writes:
This is copied from the old documentation. It used to say It is not
necessary to be concerned about the amount of time elapsed between
pg_start_backup and the start
On Sun, Jun 17, 2012 at 11:42 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
Is there a reason why we don't have a parameter on the client
mirroring ssl_ciphers?
Dunno, do we need one? I am not sure what the cipher negotiation process
looks like or which
On Sat, Jun 16, 2012 at 12:55 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
Yes, but there's also a lot of such awkward logic we need to add if we
*do* go with the SSL library doing the compression:
For example, we can no longer trust the SSL library
On Sat, Jun 16, 2012 at 12:40 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Marko Kreen mark...@gmail.com writes:
On Sat, Jun 16, 2012 at 6:39 AM, Magnus Hagander mag...@hagander.net wrote:
Fair enough if we decide that - but we should make that decision
knowing that we're leaving the JDBC and .Net
JOIN t1 ON t2.b=t1.z
)
I get a syntax error on the RECURSIVE.
Is there any other position in this query that I can put the RECURSIVE
in order for it to get through?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list
On Sat, Jun 16, 2012 at 2:52 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
Basically, I'd like to combine a recursive and a non-recursive CTE in
the same query.
Just mark them all as recursive. There's no harm in marking a CTE as
recursive when it isn't
1201 - 1300 of 5010 matches
Mail list logo
