, but not a context sensitive one IIRC.
--
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 Fri, Jun 28, 2013 at 5:54 AM, Kevin Grittner kgri...@ymail.com wrote:
Robert Haas robertmh...@gmail.com wrote:
Magnus Hagander mag...@hagander.net wrote:
The functionality of materialized views will (over time) totally swamp
that of normal views, so mixing all the corresponding
On Fri, Jun 28, 2013 at 4:49 PM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
Magnus Hagander escribió:
They are already crosslinked under see also. But that doesn't really
help the guy doing \h CREATE VIEW in psql, which was the case where
it was brought to my attention.
Maybe \h should
particular reason to split those up in the first place?
--
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 Thu, Jun 27, 2013 at 10:56 AM, Nicolas Barbier
nicolas.barb...@gmail.com wrote:
2013/6/27 Magnus Hagander mag...@hagander.net:
Is there a particular reason why CREATE RECURSIVE VIEW is part of the
help for CREATE VIEW, but CREATE MATERIALIZED VIEW doesn't show up
there?
I realize
. Generating those snapshots on the git server is slow and
expensive...
--
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
Is there a reason why we have set the min allowed value for port to 1,
not 1024? Given that you can't actually start postgres with a value of
1024, shoulnd't the entry in pg_settings reference that as well?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com
On Thu, Jun 27, 2013 at 2:16 PM, Peter Eisentraut pete...@gmx.net wrote:
On 6/27/13 6:34 AM, Magnus Hagander wrote:
Is there a reason why we have set the min allowed value for port to 1,
not 1024? Given that you can't actually start postgres with a value of
1024, shoulnd't the entry
something similar to this?
--
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
sends off a SIGHUP when it does
a reload. We'd have to give it an actual interface that could return
data back as well, such as a socket of some kind. So it does take some
work to come up with. But I definitely think we should have something
like this.
--
Magnus Hagander
Me: http
On Thu, Jun 20, 2013 at 2:54 PM, Dimitri Fontaine
dimi...@2ndquadrant.fr wrote:
Magnus Hagander mag...@hagander.net writes:
Should we have a way of previewing changes that would be applied if we
reloaded/restarted the server?
Yes, we should.
+1
This would go well with something I started
On Wed, Jun 19, 2013 at 4:44 AM, Peter Eisentraut pete...@gmx.net wrote:
On Tue, 2013-06-18 at 12:32 +0200, Magnus Hagander wrote:
The CF app was and is specifically for dealing with CFs. Having it
deal with backpatches makes it, well, a bugtracker. It's not meant to
be that. If we want
On Jun 19, 2013 7:55 PM, Peter Eisentraut pete...@gmx.net wrote:
On 6/19/13 1:49 PM, Josh Berkus wrote:
On 06/19/2013 10:48 AM, Peter Eisentraut wrote:
On 6/13/13 5:47 PM, Josh Berkus wrote:
2. File name to store settings set by ALTER SYSTEM command is still
persistent.auto.conf
Why?
we have the Open Items wiki page for those? Seems to work well
enough.
Yes. The CF app only tracks things that already have patches. For the
beta, we really need to track things that may not have been fixed - or
that may have been done, just only partially so far.
--
Magnus Hagander
Me: http
different
requirements.
Having an always-open CF would defeat the workflow. But since those
patches are typically going into HEAD as well, why not just a
commitfest *topic* for it, on whatever commitfest happens to be the
open one? Then it'll get processed within the existing workflow.
--
Magnus
just use a faster shutdown method (e.g. immediate)
--
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
closing the replication connection.
Imo this is a fix that needs to get backpatched... The code tried to do
this but failed, I don't think it really gives grounds for valid *new*
concerns.
+1 (without having looked at the code itself, it's definitely a
behaviour that needs to be fixed)
--
Magnus
On Jun 12, 2013 4:56 PM, Robert Haas robertmh...@gmail.com wrote:
On Sat, Jun 8, 2013 at 10:36 AM, MauMau maumau...@gmail.com wrote:
Yes, I feel designing reliable archiving, even for the simplest case -
copy
WAL to disk, is very difficult. I know there are following three
problems
if you
On Jun 6, 2013 4:14 AM, Peter Eisentraut pete...@gmx.net wrote:
On Tue, 2013-06-04 at 22:27 -0500, Karl O. Pinc wrote:
On 06/04/2013 10:16:20 PM, Peter Eisentraut wrote:
On Tue, 2013-05-07 at 23:18 -0400, Alvaro Herrera wrote:
Peter Eisentraut wrote:
On Tue, 2013-05-07 at 00:32
a unit seems like a much better idea. That way, there is no
way for confusion.
--
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
?
wfm.
+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 subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
It's been brought to my attention that I forgot to email hackers about us
adding new committers to the project, as I planned to do when I wrote my
blog post about it.
This is the same people as were announced during the pgcon closing session
- Jeff Davis, Stephen frost, fujii masao and Noah
enough to have it's own
argument if other parameters don't. And you can still set it as long
as you use psql in connection string mode, as you can with all the
libpq parameters.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers
On Tue, May 14, 2013 at 9:36 PM, Pavel Stehule pavel.steh...@gmail.com wrote:
2013/5/14 Magnus Hagander mag...@hagander.net:
psql in connection string mode
Hi Magnus, can me send some link?
http://www.postgresql.org/docs/9.2/static/app-psql.html
If this parameter contains an = sign or starts
nor the kernel adhere to that
limit...
FWIW, the tool we use to generate the commit emails truncate it at 80
(minus the pgsql: header). We can increase that, but it only fixes
the email one, and not the one that people look at on the web...
--
Magnus Hagander
Me: http://www.hagander.net/
Work
On Mon, May 6, 2013 at 4:47 PM, Andrew Dunstan and...@dunslane.net wrote:
On 05/06/2013 10:19 AM, Magnus Hagander wrote:
On Fri, May 3, 2013 at 9:07 PM, Andres Freund and...@2ndquadrant.com
wrote:
On 2013-05-03 14:54:23 -0400, Andrew Dunstan wrote:
On 05/03/2013 02:43 PM, Tom Lane wrote
On Thu, May 2, 2013 at 8:55 AM, Simon Riggs si...@2ndquadrant.com wrote:
On 26 April 2013 18:13, Heikki Linnakangas hlinnakan...@vmware.com wrote:
On 26.04.2013 19:50, Magnus Hagander wrote:
On Fri, Apr 26, 2013 at 6:43 PM, Simon Riggssi...@2ndquadrant.com
wrote:
On 26 April 2013 17:25
pg_basebackup -x (or
similar), therefor not needing the log archive at all when restoring.
Yes, it makes the base backup slightly larger, but also much
simpler... As a bonus, your base backup would still work if you hosed
your log archive.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http
On Apr 26, 2013 4:38 PM, Robert Haas robertmh...@gmail.com wrote:
On Fri, Apr 26, 2013 at 10:05 AM, Simon Riggs si...@2ndquadrant.com
wrote:
Restore points are definitely the way to go here, this is what they
were created for. Stopping at a labelled location has a defined
meaning for the
a cleaner syntax to break
those.
--
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
i tried all worked...
made that we don't have to support the historical URLs for our
archives pages, I think that's a really bad plan; those links are in a
lot more places than just the Todo.
No, the plan has always been to support those. There are no plans to
remove that.
--
Magnus
On Wed, Apr 17, 2013 at 3:14 PM, Robert Haas robertmh...@gmail.com wrote:
On Wed, Apr 17, 2013 at 8:48 AM, Magnus Hagander mag...@hagander.net wrote:
Yes. We can infer that. It makes it a whole lot easier to fix
something with better bug repors than that, of course, as I'm sure you
(Robert
, but there will be no
official patch for 8.3.
--
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
are
the others from?
--
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 Mon, Apr 1, 2013 at 9:09 PM, Andres Freund and...@2ndquadrant.com wrote:
Hi,
On 2013-04-01 20:43:36 +0200, Magnus Hagander wrote:
Maybe my thinking is just missing something obvious here. But looking
at a fresh initdb, I'm seeing a number of files in the data directory
for this database
On Mon, Apr 1, 2013 at 10:53 PM, Andres Freund and...@2ndquadrant.com wrote:
On 2013-04-01 21:24:06 +0200, Magnus Hagander wrote:
On Mon, Apr 1, 2013 at 9:09 PM, Andres Freund and...@2ndquadrant.com wrote:
Hi,
On 2013-04-01 20:43:36 +0200, Magnus Hagander wrote:
Maybe my thinking is just
to push another one
just one (or even two) weeks after that would be rushing it
unnecessarily...
Of course, that doesn't prevent from starting work on the release
notes meanwhile :)
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql
by the invalid push that Kevin did a short while ago...
--
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
?
If it's just a doc thing - perhaps this is a table we should somehow
try to autogenerate?
--
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 Mar 20, 2013 11:14 PM, Dimitri Fontaine dimi...@2ndquadrant.fr wrote:
Atri Sharma atri.j...@gmail.com writes:
We can use a scheduling algorithm, and can define a pool of tasks as
well as
a time constraint for the amount of time which can be used for running
the
tasks.Then, a scheduling
it, and can give
a nice error message telling the user how to deal with it.
--
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 Mar 13, 2013 3:04 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Palle Girgensohn gir...@freebsd.org writes:
... I got lots of space freed
up, but it seems that after that the disk usage grows linearly (it seems
to leave many inodes unreferenced).
Hm. We've seen issues in the past with PG
On Sun, Jan 20, 2013 at 5:56 PM, Dean Rasheed dean.a.rash...@gmail.com wrote:
On 5 January 2013 16:58, Magnus Hagander mag...@hagander.net wrote:
Attached is an updated version of the patch, per the comments from Tom
and rebased on top of the current master. Since it's been a long time
ago
On Mar 4, 2013 10:55 AM, Boszormenyi Zoltan z...@cybertec.at wrote:
2013-03-04 08:02 keltezéssel, Simon Riggs írta:
On 4 March 2013 06:39, Boszormenyi Zoltan z...@cybertec.at wrote:
commit 3bf3ab8c563699138be02f9dc305b7b77a724307
(Add a materialized view relations.) added this:
needs an extra exclusion
for this special case?
--
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 Mon, Mar 4, 2013 at 8:34 AM, Magnus Hagander mag...@hagander.net wrote:
Committers,
please hold *all* pushes to the PostgreSQL repository until we have
resolved the issue mentioned in
http://www.postgresql.org/message-id/cabuevezm2f8qaxvds9me-41l5bqeego4duoscqhc0c6v05h...@mail.gmail.com
On Mon, Mar 4, 2013 at 8:54 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
AFAICT, there's a bug in tm2timestamp(). You can't do this:
postgres=# select '1999-12-31T24:00:00'::timestamptz;
ERROR: timestamp out of range: 1999-12-31T24:00:00
But that's
, and you may need to re-push it again anyway.. So
please just hold off until we've sorted out that issue.
--
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
+1 on changing the deprecation message. And don't
forget to backpatch the change so it shows up in the old versions of
the docs as well.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
On Feb 20, 2013 11:29 AM, Heikki Linnakangas hlinnakan...@vmware.com
wrote:
On 20.02.2013 02:11, Selena Deckelmann wrote:
So, I just ran into a similar issue backing up a 9.2.1 server using
pg_basebackup version 9.2.3:
pg_basebackup: starting background WAL receiver
pg_basebackup:
On Wed, Feb 20, 2013 at 4:53 PM, Selena Deckelmann sel...@chesnok.com wrote:
On Wed, Feb 20, 2013 at 6:23 AM, Magnus Hagander mag...@hagander.net
wrote:
On Feb 20, 2013 11:29 AM, Heikki Linnakangas hlinnakan...@vmware.com
wrote:
On 20.02.2013 02:11, Selena Deckelmann wrote:
So, I
.
--
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
in general that contains such
references, it could be dropped.
--
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, Feb 12, 2013 at 4:22 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
On Tue, Feb 12, 2013 at 10:19 AM, Dave Page dp...@pgadmin.org wrote:
The phrasing as of 8.2 basically means from 8.2 onwards. Changing the
version there would make the text incorrect
On Mon, Feb 11, 2013 at 5:01 AM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
Magnus Hagander escribió:
On Sun, Feb 10, 2013 at 3:25 AM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
I changed the defaults for new subscribers, and also the flags values
for all existing subscribers, note
On Mon, Feb 11, 2013 at 2:44 PM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
Magnus Hagander escribió:
On Mon, Feb 11, 2013 at 5:01 AM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
Magnus Hagander escribió:
On Sun, Feb 10, 2013 at 3:25 AM, Alvaro Herrera
alvhe...@2ndquadrant.com
On Sun, Feb 10, 2013 at 3:25 AM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
Magnus Hagander escribió:
On Sat, Feb 9, 2013 at 4:31 PM, Peter Geoghegan
peter.geoghega...@gmail.com wrote:
On 9 February 2013 15:24, Magnus Hagander mag...@hagander.net wrote:
It's in your personal majordomo
-0500
with subject
Re: pg_prewarm
is currently being delivered.
--
Gurjeet Singh
http://gurjeet.singh.im/
--
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
On Sat, Feb 9, 2013 at 4:31 PM, Peter Geoghegan
peter.geoghega...@gmail.com wrote:
On 9 February 2013 15:24, Magnus Hagander mag...@hagander.net wrote:
It's in your personal majordomo settings. I don't think it's related
to that at all, but it's a flag you set on your subscription, so
perhaps
broken to
any newcomer.
I agree it's way too many step. Several of those can certainly be made
more efficient now that we have a more sane archives, well within the
scope of the current system.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via
On Fri, Feb 8, 2013 at 6:49 AM, Etsuro Fujita
fujita.ets...@lab.ntt.co.jp wrote:
I found a comment typo. Please find attached a patch.
Applied, thanks.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql
On Fri, Feb 8, 2013 at 4:20 PM, Peter Eisentraut pete...@gmx.net wrote:
On 2/8/13 5:23 AM, Magnus Hagander wrote:
But do you have any actual proof that the problem is in we
loose reviewers because we're relying on email?
Here is one: Me.
Just yesterday I downloaded a piece of software
On Fri, Feb 8, 2013 at 6:53 PM, Robert Haas robertmh...@gmail.com wrote:
On Fri, Feb 8, 2013 at 11:09 AM, Kevin Grittner kgri...@ymail.com wrote:
Magnus Hagander mag...@hagander.net wrote:
if there is any other committer who [wants to receive emails from
the packagers list], let me know and I
and forth between the CF app and your mail reader. But it's still
only on the annoyance side, I think the process in general is not
broken. (That said, I *have* been on the inside a long time, *and* I
live in Stockholm, so I might well have that syndrome)
--
Magnus Hagander
Me: http://www.hagander.net
to happen)
--
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
with 128Mb RAM...
--
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 Feb 5, 2013 5:34 PM, Andrew Dunstan and...@dunslane.net wrote:
On 02/01/2013 08:55 AM, Andrew Dunstan wrote:
On 02/01/2013 06:12 AM, Craig Ringer wrote:
On 01/26/2013 10:56 PM, Noah Misch wrote:
On Sat, Jan 26, 2013 at 12:20:56PM +0800, Craig Ringer wrote:
Just to confirm, I think
On Feb 3, 2013 4:16 AM, Phil Sorber p...@omniti.com wrote:
This patch came up from discussion about pg_isready.
PQconninfoParseParams is similar to PQconninfoParse but takes two
arrays like PQconnectdbParams. It essentially exposes
conninfo_array_parse().
PQconninfodefaultsMerge
On Thu, Jan 24, 2013 at 7:04 AM, Hari Babu haribabu.ko...@huawei.com wrote:
On Wed, Jan 23, 2013 11:48 PM, Magnus Hagander wrote:
On Wed, Jan 23, 2013 at 10:18 AM, Hari Babu haribabu.ko...@huawei.com
wrote:
Test scenario to reproduce:
1. Start the server
2. create the user
On Tue, Jan 22, 2013 at 7:31 AM, Amit Kapila amit.kap...@huawei.com wrote:
On Monday, January 21, 2013 6:22 PM Magnus Hagander
On Fri, Jan 18, 2013 at 7:50 AM, Amit Kapila amit.kap...@huawei.com
wrote:
On Wednesday, January 16, 2013 4:02 PM Heikki Linnakangas wrote:
On 07.01.2013 16:23
On Sun, Jan 20, 2013 at 4:59 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
+ PGresult *res = ExecuteSqlQueryForSingleRow(fout, SELECT
pg_is_in_recovery());
That function call needs to be schema-qualified for security.
Applied and backpatched
On Fri, Jan 25, 2013 at 1:59 PM, Andres Freund and...@2ndquadrant.com wrote:
On 2013-01-25 13:56:11 +0100, Magnus Hagander wrote:
On Fri, Jan 25, 2013 at 1:31 PM, Andres Freund and...@2ndquadrant.com
wrote:
On 2013-01-25 08:49:10 +, Magnus Hagander wrote:
Make pg_dump exclude unlogged
it will be 2.1.9 that's included in the next debian stable.
--
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 do it for you, but I'm pretty sure it's
impossible to do it as an archive_command there.
--
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, Jan 24, 2013 at 6:25 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
On Thu, Jan 24, 2013 at 6:04 PM, Peter Eisentraut pete...@gmx.net wrote:
I think it might be better to just document this as an example. I don't
quite see the overhead
recovery.conf file look like?
--
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 Mon, Jan 21, 2013 at 9:01 AM, Andrew Dunstan and...@dunslane.net wrote:
On 01/21/2013 02:17 AM, Magnus Hagander wrote:
On Jan 21, 2013 3:06 AM, Craig Ringer cr...@2ndquadrant.com
mailto:cr...@2ndquadrant.com wrote:
On 01/21/2013 10:03 AM, Craig Ringer wrote:
On 01/19/2013 04:08 AM
or something else), it might be generic
and can be used for others as well but it might need few interface changes.
If it's specifying them that is cumbersome, then that's the part we
should fix, rather than modifying the protocol, no?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http
starting each build step takes
significantly longer. We've also added some things like the DEF file
magic that can definitely take quite some time, particularly when
building the backend.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql
On Jan 22, 2013 1:31 AM, Robert Haas robertmh...@gmail.com wrote:
On Mon, Jan 21, 2013 at 6:23 PM, Phil Sorber p...@omniti.com wrote:
On Wed, Jan 16, 2013 at 8:18 AM, Abhijit Menon-Sen a...@2ndquadrant.com
wrote:
Here's a breakdown based purely on the names from the CF page (i.e. I
didn't
On Tue, Jan 15, 2013 at 10:35 PM, Magnus Hagander mag...@hagander.net wrote:
On Tue, Jan 15, 2013 at 12:13 AM, j...@tanga.com wrote:
The following bug has been logged on the website:
Bug reference: 7809
Logged by: Joe Van Dyk
Email address: j...@tanga.com
PostgreSQL
missing something?
--
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, Jan 20, 2013 at 4:59 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
+ PGresult *res = ExecuteSqlQueryForSingleRow(fout, SELECT
pg_is_in_recovery());
That function call needs to be schema-qualified for security.
Ha! I wonder if I can
On Jan 21, 2013 3:06 AM, Craig Ringer cr...@2ndquadrant.com wrote:
On 01/21/2013 10:03 AM, Craig Ringer wrote:
On 01/19/2013 04:08 AM, Boszormenyi Zoltan wrote:
However, I am not sure whether Cygwin provides the mkstemp() call or
not.
Searching... Found bugzilla reports against mkstemp on
* support connection strings.
And, an important point, do it the same way.
--
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
it and it didn't work. We pushed
the whole implementation to next version (and then forgot about
actually putting it in the next version, until now)
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
On Jan 17, 2013 8:15 AM, Abhijit Menon-Sen a...@2ndquadrant.com wrote:
At 2013-01-17 16:05:05 +0900, michael.paqu...@gmail.com wrote:
Is it really necessary to create a new commit fest just to move the
items? Marking the patches that are considered as being too late for
9.3 should be
for them to do a second-stage review even if somebody
else has done the first 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
that, then we can
commit it as a partial feature, but if we just hope someone picks it
up, that's leaving it very loose..
--
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, Jan 17, 2013 at 11:09 AM, Dave Page dp...@pgadmin.org wrote:
On Thu, Jan 17, 2013 at 9:36 AM, Magnus Hagander mag...@hagander.net wrote:
On Thu, Jan 17, 2013 at 2:35 AM, Tatsuo Ishii is...@postgresql.org wrote:
This might be way more than we want to do, but there is an article
.
Attached is a v6 patch, with no tabs in docs and based
off the latest head.
I'm marking it ready for committer.
Thanks. Applied, with only some small whitespace changes.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers
-downloads-and-installs it as necessary we can get around that)
--
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
On Sun, Dec 16, 2012 at 7:20 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
On Sat, Dec 15, 2012 at 2:24 PM, Erik Rijkers e...@xs4all.nl wrote:
That would make such a truncation less frequent, and after all a truncated
display is not
particular useful
On Wed, Jan 2, 2013 at 3:17 PM, Magnus Hagander mag...@hagander.net wrote:
On Wed, Jan 2, 2013 at 3:15 PM, Noah Misch n...@leadboat.com wrote:
On Wed, Jan 02, 2013 at 02:03:20PM +0100, Magnus Hagander wrote:
On Wed, Jan 2, 2013 at 1:15 AM, Tom Lane t...@sss.pgh.pa.us wrote:
So +1 for changing
and discussing things that will happen that far ahead is
definitely not focusing on review.
--
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
put more work into it.
We also talked about the one-patch-one-review. Did someone ever check
if that worked out - did we get that spread, or did we end up with the
same ratio as last time?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql
to nominate Craig Ringer to be independent CF mgr for Jan2013 CF.
If he's willing to do that, then +1 from me.
--
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
of saying could not open file, could we find a way to
say this is an unlogged table on a slave, it's not going to work?
We can fix pg_dump the easy way, but what about custom tools...
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql
On Sat, Jan 5, 2013 at 3:11 PM, Magnus Hagander mag...@hagander.net wrote:
On Fri, Jan 4, 2013 at 7:13 PM, Peter Eisentraut pete...@gmx.net wrote:
On 1/3/13 12:30 PM, Robert Haas wrote:
On Thu, Jan 3, 2013 at 11:32 AM, Magnus Hagander mag...@hagander.net
wrote:
Any particular reason? It goes
for quite a while before we got
standby_mode=on, I believe we should have pg_retainxlog (or something
like it) until we have something more integrated.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers
1001 - 1100 of 4943 matches
Mail list logo
