On Thu, Jan 9, 2014 at 12:34 PM, Mark Dilger markdil...@yahoo.com wrote:
Michael Paquier wrote:
A possible input for a test that users could provide would be something
like that:
# Node information for tests
nodes {
{node1, postgresql.conf params, recovery.conf params}
{node2
On Fri, Jan 10, 2014 at 12:08 AM, MauMau maumau...@gmail.com wrote:
C2. recovery_target = 'immediate' sounds less intuitive than my suggestion
recovery_target_time = 'backup_point', at least for those who want to
recover to the backup point.
Although I don't have a good naming sense in
On Fri, Jan 10, 2014 at 3:23 AM, Simon Riggs si...@2ndquadrant.com wrote:
On 8 January 2014 21:40, Tom Lane t...@sss.pgh.pa.us wrote:
Kevin Grittner kgri...@ymail.com writes:
I'm torn on whether we should cave to popular demand on this; but
if we do, we sure need to be very clear in the
Hi all,
This is perhaps something that has already been discussed on hackers,
I just could not find anything in the archives.
Currently, pg_start_backup and pg_stop_backup cannot run on a standby
because it is not possible to write a backup_label file to disk,
because of the nature of a standby
Hi,
On Tue, Jan 14, 2014 at 4:28 PM, Yugo Nagata nag...@sraoss.co.jp wrote:
Here is the patch to implement to_regclass, to_regproc, to_regoper,
and to_regtype. They are new functions similar to regclass, regproc,
regoper, and regtype except that if requested object is not found,
returns
Hi all,
As of today, replication protocol has a command called BASE_BACKUP to
allow a client connecting with the replication protocol to retrieve a
full backup from server through a connection stream. The description
of its current options are here:
On Tue, Jan 14, 2014 at 10:01 PM, Heikki Linnakangas
hlinnakan...@vmware.com wrote:
- Addition of an option called INCREMENTAL to send an incremental
backup to the client. This option uses as input an LSN, and sends back
to client relation pages (in the shape of reduced relation files) that
On Tue, Jan 14, 2014 at 10:12 PM, Magnus Hagander mag...@hagander.net wrote:
On Tue, Jan 14, 2014 at 1:47 PM, Michael Paquier michael.paqu...@gmail.com
wrote:
Hi all,
As of today, replication protocol has a command called BASE_BACKUP to
allow a client connecting with the replication
On Wed, Jan 15, 2014 at 10:27 AM, Vik Fearing vik.fear...@dalibo.com wrote:
On 12/26/2013 06:10 PM, David Fetter wrote:
On Tue, Dec 24, 2013 at 07:25:01PM +0100, Vik Fearing wrote:
I was recently annoyed that I had to do
CREATE TABLESPACE x LOCATION y;
ALTER TABLESPACE x SET
On Wed, Jan 15, 2014 at 4:32 AM, Robert Haas robertmh...@gmail.com wrote:
On Tue, Jan 14, 2014 at 1:54 PM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
Robert Haas escribió:
On Tue, Jan 14, 2014 at 12:43 PM, Thom Brown t...@linux.com wrote:
LOG: worker process: test_shm_mq (PID 22041)
On Wed, Jan 15, 2014 at 2:02 PM, Jim Nasby j...@nasby.net wrote:
You know, this doesn't do much to encourage people to submit patches since
it was just suggested that we use WITH instead of SET. :(
Sorry, you are right.
Anyone have an easy way to see which is more prevalent? I'd be stuck with
On Fri, Jan 17, 2014 at 5:03 AM, Andres Freund and...@2ndquadrant.com wrote:
slightly related: we should start to reuse procLatch for walsenders
instead of having a separate latch someday.
+ 1 on that.
--
Michael
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
On Thu, Jan 16, 2014 at 9:03 AM, Vik Fearing vik.fear...@dalibo.com wrote:
New patch attached, with regression tests.
Thanks for the new version, I have spent some time looking at it:
- Patch compiles without warnings.
- Done some manual testing with CREATE/ALTER TABLESPACE WITH and
checked
be fixed :)
Regards,
--
Michael
commit 9886e788b27c8fce895ccea4c83ddd223bc2
Author: Michael Paquier mich...@otacoo.com
Date: Sat Jan 18 13:38:59 2014 +0900
Fix typos and temporary file management in ALTER SYSTEM
Using a temporary file uniquely defined in a single place reduces
On Mon, Jan 20, 2014 at 2:12 PM, Amit Kapila amit.kapil...@gmail.com wrote:
On Sat, Jan 18, 2014 at 7:59 PM, Michael Paquier
michael.paqu...@gmail.com wrote:
Hi all,
After going through commit 65d6e4c (introducing ALTER SYSTEM SET), I
noticed a couple of typo mistakes as well as (I think
On Wed, Jan 22, 2014 at 5:29 AM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
I agree with Michael that having pg_basebackup be aware of the .temp
suffix is ugly; for instance if we were to fix it to .tmp in ALTER
SYSTEM but forgot to change pg_basebackup, the check would be
immediately
On Thu, Jan 9, 2014 at 6:36 AM, Gabriele Bartolini
gabriele.bartol...@2ndquadrant.it wrote:
Il 08/01/14 18:42, Simon Riggs ha scritto:
Not sure I see why it needs to be an SRF. It only returns one row.
Attached is version 4, which removes management of SRF stages.
I have been looking at v4 a
On Sat, Jan 25, 2014 at 5:41 AM, Fujii Masao masao.fu...@gmail.com wrote:
On Thu, Jan 23, 2014 at 4:10 PM, Michael Paquier
michael.paqu...@gmail.com wrote:
On Thu, Jan 9, 2014 at 6:36 AM, Gabriele Bartolini
gabriele.bartol...@2ndquadrant.it wrote:
Il 08/01/14 18:42, Simon Riggs ha scritto
On Sat, Jan 25, 2014 at 5:10 AM, Heikki Linnakangas
hlinnakan...@vmware.com wrote:
Thanks, committed!
It seems that this patch has not been pushed :)
Regards,
--
Michael
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
On Sat, Jan 25, 2014 at 3:19 PM, Michael Paquier
michael.paqu...@gmail.com wrote:
On Sat, Jan 25, 2014 at 5:41 AM, Fujii Masao masao.fu...@gmail.com wrote:
On Thu, Jan 23, 2014 at 4:10 PM, Michael Paquier
michael.paqu...@gmail.com wrote:
On Thu, Jan 9, 2014 at 6:36 AM, Gabriele Bartolini
Hi,
Please find attached an updated patch (context diffs) improving the
comments related to ALTER SYSTEM. This patch does nothing for the
suffix tmp/temp used in a couple of places of the code, it only
corrects some typos and makes the comments more consistent with
current code.
The
On Mon, Jan 27, 2014 at 11:29 AM, Michael Paquier
michael.paqu...@gmail.com wrote:
Hi,
Please find attached an updated patch (context diffs) improving the
comments related to ALTER SYSTEM. This patch does nothing for the
suffix tmp/temp used in a couple of places of the code, it only
On Mon, Jan 27, 2014 at 12:49 PM, Fujii Masao masao.fu...@gmail.com wrote:
On Mon, Jan 27, 2014 at 11:53 AM, Michael Paquier
michael.paqu...@gmail.com wrote:
On Mon, Jan 27, 2014 at 11:29 AM, Michael Paquier
michael.paqu...@gmail.com wrote:
Hi,
Please find attached an updated patch (context
On Tue, Jan 28, 2014 at 12:56 PM, Fujii Masao masao.fu...@gmail.com wrote:
Hi,
The files in pg_stat_tmp directory don't need to be backed up because they are
basically reset at the archive recovery. So I think it's worth
changing pg_basebackup
so that it skips any files in pg_stat_tmp
On Tue, Jan 28, 2014 at 2:29 PM, David Fetter da...@fetter.org wrote:
On Tue, Jan 28, 2014 at 04:48:35PM +1300, Gavin Flower wrote:
On 28/01/14 16:33, Andrew Dunstan wrote:
On 01/27/2014 10:24 PM, Sawada Masahiko wrote:
Hi all,
Attached patch fixes the typo which is in
On Wed, Jan 29, 2014 at 3:03 AM, Fujii Masao masao.fu...@gmail.com wrote:
On Tue, Jan 28, 2014 at 3:42 AM, Fujii Masao masao.fu...@gmail.com wrote:
On Sat, Jan 25, 2014 at 3:19 PM, Michael Paquier
michael.paqu...@gmail.com wrote:
On Sat, Jan 25, 2014 at 5:41 AM, Fujii Masao masao.fu
On Wed, Jan 29, 2014 at 10:55 AM, Fujii Masao masao.fu...@gmail.com wrote:
On Wed, Jan 29, 2014 at 3:07 AM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
Anybody knows about this patch?
http://www.postgresql.org/message-id/508dfec9.4020...@uptime.jp
Though I'm not sure whether Nagayasu is
Hi all,
The undocumented GUC called xloginsert_slots has been introduced by
commit 9a20a9b. It is mentioned by the commit that this parameter
should be removed before the release. Wouldn't it be a good time to
remove this parameter soon? I imagine that removing it before the beta
would make sense
On Sat, Jan 25, 2014 at 5:41 AM, Fujii Masao masao.fu...@gmail.com wrote:
I think that it's time to rename all the variables related to
pg_stat_bgwriter.
For example, it's better to change PgStat_GlobalStats to PgStat_Bgwriter.
I think that it's okay to make this change as separate patch,
On Wed, Jan 29, 2014 at 10:38 PM, Michael Paquier
michael.paqu...@gmail.com wrote:
On Sat, Jan 25, 2014 at 5:41 AM, Fujii Masao masao.fu...@gmail.com wrote:
I think that it's time to rename all the variables related to
pg_stat_bgwriter.
For example, it's better to change PgStat_GlobalStats
On Fri, Jan 31, 2014 at 6:09 AM, Robert Haas robertmh...@gmail.com wrote:
On Thu, Jan 30, 2014 at 3:32 AM, Christian Kruse
christ...@2ndquadrant.com wrote:
For the documentation patch, I propose the attached to avoid future
confusions. Comments? It might make sense to back-patch as well.
On Sat, Feb 1, 2014 at 12:42 AM, Robert Haas robertmh...@gmail.com wrote:
On Fri, Jan 31, 2014 at 2:28 AM, Michael Paquier
michael.paqu...@gmail.com wrote:
I took a look at this with a view to committing it but on examination
I'm not sure this is the best way to proceed. The proposed text
On Sat, Feb 1, 2014 at 6:37 AM, Bruce Momjian br...@momjian.us wrote:
On Mon, Aug 5, 2013 at 04:20:40PM +0900, Michael Paquier wrote:
Hi all,
By having a look at the documentation of SELECT, it is not specified that FOR
SHARE/UPDATE and friends are incompatible with the clauses in $subject
On Wed, Jan 29, 2014 at 3:03 AM, Fujii Masao masao.fu...@gmail.com wrote:
On Tue, Jan 28, 2014 at 3:42 AM, Fujii Masao masao.fu...@gmail.com wrote:
On Sat, Jan 25, 2014 at 3:19 PM, Michael Paquier
michael.paqu...@gmail.com wrote:
On Sat, Jan 25, 2014 at 5:41 AM, Fujii Masao masao.fu
On Fri, Dec 13, 2013 at 2:47 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Andres Freund and...@2ndquadrant.com writes:
On 2013-12-12 11:55:51 -0500, Tom Lane wrote:
I'm not, however, terribly thrilled with the suggestions to add implicit
casts associated with this type. Implicit casts are generally
On Sun, Feb 2, 2014 at 2:43 AM, Gabriele Bartolini
gabriele.bartol...@2ndquadrant.it wrote:
Hi Michael and Fujii,
Il 01/02/14 17:46, Fujii Masao ha scritto:
I think that it's OK to add that as TODO item. There might be
the system that the speed of WAL archiving is slower than
that of WAL
On Sun, Feb 2, 2014 at 12:07 AM, Andres Freund and...@2ndquadrant.com wrote:
On 2014-02-02 00:04:41 +0900, Michael Paquier wrote:
On Fri, Dec 13, 2013 at 2:47 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Andres Freund and...@2ndquadrant.com writes:
On 2013-12-12 11:55:51 -0500, Tom Lane wrote
On Tue, Feb 4, 2014 at 10:10 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Michael Paquier michael.paqu...@gmail.com writes:
Please find attached a patch implementing lsn as a datatype, based on
the one Robert wrote a couple of years ago.
Patch contains regression tests as well as a bit
On Tue, Feb 4, 2014 at 12:49 AM, Robert Haas robertmh...@gmail.com wrote:
On Fri, Jan 31, 2014 at 5:48 PM, Michael Paquier
michael.paqu...@gmail.com wrote:
The part about the planning parameter looks good, thanks. The places
used to mention the databases used also makes more sense. Thanks
On Tue, Feb 4, 2014 at 6:15 PM, Andres Freund and...@2ndquadrant.com wrote:
+ /*--
+ * Relational operators for LSNs
+ *-*/
Isn't it just operators? They aren't really
On Tue, Feb 4, 2014 at 7:22 PM, Andres Freund and...@2ndquadrant.com wrote:
On 2014-02-04 19:17:51 +0900, Michael Paquier wrote:
@@ -180,7 +175,7 @@ pg_get_replication_slots(PG_FUNCTION_ARGS)
else
nulls[i++] = true;
if (restart_lsn
On Wed, Feb 5, 2014 at 5:26 AM, Peter Eisentraut pete...@gmx.net wrote:
Perhaps this type should be called pglsn, since it's an
implementation-specific detail and not a universal concept like int,
point, or uuid.
It makes sense. I'll update the patches according to that.
--
Michael
--
Sent
On Wed, Feb 5, 2014 at 7:22 AM, Jeremy Harris j...@wizmail.org wrote:
The attached patch replaces the existing siftup method for heapify with
a siftdown method. Tested with random integers it does 18% fewer
compares and takes 10% less time for the heapify, over the work_mem
range 1024 to
On Wed, Feb 5, 2014 at 9:38 AM, Michael Paquier
michael.paqu...@gmail.com wrote:
On Wed, Feb 5, 2014 at 8:59 AM, Michael Paquier
michael.paqu...@gmail.com wrote:
I'll update the patches according to that.
Here are the updated patches with the following changes (according to
previous comments
On Wed, Feb 5, 2014 at 10:33 AM, Jon Nelson jnelson+pg...@jamponi.net wrote:
What - if anything - do I need to do to get this on the commitfest
list for the next commitfest?
The list of instructions is here:
http://wiki.postgresql.org/wiki/Submitting_a_Patch#Patch_submission
Then the next commit
On Wed, Feb 5, 2014 at 3:14 PM, Amit Kapila amit.kapil...@gmail.com wrote:
On Wed, Feb 5, 2014 at 10:30 AM, James Sewell james.sew...@lisasoft.com
I've seen some proposals and a tool (pg_rewind), but all seem to have draw
backs.
As far as I remember, one of the main drawbacks for pg_rewind
On Fri, Feb 7, 2014 at 1:18 AM, Andrew Dunstan and...@dunslane.net wrote:
On 02/01/2014 05:20 PM, Andres Freund wrote:
diff --git a/src/backend/utils/adt/Makefile
b/src/backend/utils/adt/Makefile
index 1ae9fa0..fd93d9b 100644
--- a/src/backend/utils/adt/Makefile
+++
On Fri, Feb 7, 2014 at 1:57 PM, James Sewell james.sew...@lisasoft.comwrote:
I've just noticed that on PostgreSQL 9.3 I can do the following with a
master node A and a slave node B (as long as I have set
recovery_target_timeline = 'latest'):
1. Stop Node A
2. Promote Node B
3.
On Fri, Feb 7, 2014 at 3:02 PM, James Sewell james.sew...@lisasoft.comwrote:
Node A could get ahead even if it has been shut down cleanly BEFORE the
promotion?
I'd always assumed if I shut down the master the slave would be at the
same point after shutdown - is this incorrect?
Yes and no. A
On Thu, Feb 6, 2014 at 11:26 AM, Michael Paquier
michael.paqu...@gmail.com wrote:
Here are updated patches to use pg_lsn instead of pglsn...
Should I register this patch somewhere to avoid having it lost in the void?
Regards,
--
Michael
--
Sent via pgsql-hackers mailing list (pgsql-hackers
On Mon, Feb 17, 2014 at 6:28 PM, Andres Freund and...@2ndquadrant.com wrote:
I don't think this really has gone above Needs Review yet.
I am not sure that this remark makes the review of this patch much
progressing :(
By the way, I spent some time looking at it and here are some comments:
-
On Tue, Feb 18, 2014 at 7:22 AM, Andres Freund and...@2ndquadrant.com wrote:
On 2014-02-17 23:07:45 +0900, Michael Paquier wrote:
On Mon, Feb 17, 2014 at 6:28 PM, Andres Freund and...@2ndquadrant.com
wrote:
I don't think this really has gone above Needs Review yet.
I am not sure
On Tue, Feb 18, 2014 at 12:43 PM, Amit Kapila amit.kapil...@gmail.com wrote:
Description for contents of PGDATA is mentioned at
following page in docs:
http://www.postgresql.org/docs/devel/static/storage-file-layout.html
Isn't it better to have description of pg_replslot in the same
place?
On Tue, Feb 18, 2014 at 1:29 AM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
MauMau escribió:
The pg_regress part is ugly. However, pg_regress is doing something
unusual when starting postmaster itself, so the ugly coding to stop it
seems to match. If we wanted to avoid the ugliness here,
This patch is in Waiting for Author for a couple of weeks and has
received a review at least from Andres during this commit fest. As the
situation is not much progressing, I am going to mark it as Returned
with feedback.
If there are any problems with that please let me know.
Thanks,
--
Michael
On Thu, Feb 20, 2014 at 2:47 AM, Robert Haas robertmh...@gmail.com wrote:
On Wed, Feb 5, 2014 at 9:26 PM, Michael Paquier
michael.paqu...@gmail.com wrote:
On Thu, Feb 6, 2014 at 3:48 AM, Peter Eisentraut pete...@gmx.net wrote:
On 2/5/14, 1:31 PM, Robert Haas wrote:
On Tue, Feb 4, 2014 at 3:26
On Thu, Feb 20, 2014 at 1:01 AM, David Fetter da...@fetter.org wrote:
On Tue, Feb 18, 2014 at 04:39:27PM -0300, Alvaro Herrera wrote:
Heikki Linnakangas wrote:
Add a GUC to report whether data page checksums are enabled.
Is there are reason this wasn't back-patched to 9.3? I think it should
On Thu, Feb 20, 2014 at 9:43 AM, Michael Paquier
michael.paqu...@gmail.com wrote:
On Thu, Feb 20, 2014 at 2:47 AM, Robert Haas robertmh...@gmail.com wrote:
On Wed, Feb 5, 2014 at 9:26 PM, Michael Paquier
michael.paqu...@gmail.com wrote:
On Thu, Feb 6, 2014 at 3:48 AM, Peter Eisentraut pete
On Thu, Feb 20, 2014 at 8:55 AM, Andres Freund and...@2ndquadrant.com wrote:
On 2014-02-19 12:47:40 -0500, Robert Haas wrote:
On Wed, Feb 5, 2014 at 9:26 PM, Michael Paquier
michael.paqu...@gmail.com wrote:
Yes, that's a good precedent in multiple ways.
Here are updated patches to use
Hi,
While compiling on clang, I noticed the following warning:
pg_backup_archiver.c:1950:32: warning: comparison of constant -1 with
expression of type 'ArchiveFormat' (aka 'enum _archiveFormat') is always
false
[-Wtautological-constant-out-of-range-compare]
if ((AH-format =
Hi all,
Please find attached a patch to dump pageinspect to 1.2. This simply
changes page_header to use the new internal datatype pg_lsn instead of text.
Regards,
--
Michael
diff --git a/contrib/pageinspect/Makefile b/contrib/pageinspect/Makefile
index 0e267eb..ee78cb2 100644
---
On Sun, Feb 23, 2014 at 6:09 AM, Alvaro Herrera alvhe...@2ndquadrant.comwrote:
Michael Paquier escribió:
Hi all,
Please find attached a patch to dump pageinspect to 1.2. This simply
changes page_header to use the new internal datatype pg_lsn instead of
text.
Uhm. Does this crash
On Tue, Feb 25, 2014 at 12:41 AM, Robert Haas robertmh...@gmail.com wrote:
On Wed, Feb 19, 2014 at 8:27 PM, Michael Paquier
michael.paqu...@gmail.com wrote:
On Thu, Feb 20, 2014 at 8:55 AM, Andres Freund and...@2ndquadrant.com
wrote:
On 2014-02-19 12:47:40 -0500, Robert Haas wrote
On Mon, Feb 24, 2014 at 11:34 PM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
Andres Freund escribió:
On 2014-02-24 17:53:31 +0900, Michael Paquier wrote:
On Sun, Feb 23, 2014 at 6:09 AM, Alvaro Herrera
alvhe...@2ndquadrant.comwrote:
Michael Paquier escribió:
Hi all
On Tue, Feb 25, 2014 at 10:02 AM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
While we're messing with this, I wonder if there's any way to have
infomask and infomask2 displayed in hex format rather than plain int
without having to specify that in every query. I'm not well known for
being
On Wed, Feb 26, 2014 at 5:45 AM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
Robert Haas escribió:
On Mon, Feb 24, 2014 at 9:34 AM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
Yeah, erroring out seems good enough. Particularly if you add a hint
saying please upgrade the extension.
Hi all,
When working on the datatype pg_lsn, we actually did not create a
define macro for its oid in pg_type.h and this could be useful for
extension developers. The simple patch attached corrects that by
naming this macro LSNOID.
Regards,
--
Michael
diff --git a/src/include/catalog/pg_type.h
Thanks for your patch!
On Fri, Feb 28, 2014 at 4:18 PM, pgsql...@postgresql.kr wrote:
I patched to add one column in pg_stat_statements module.
and sent to author but
I need a last time of query, because I want to analyse order by recent time.
Hm... I am not sure that this brings much to
On Sun, Mar 2, 2014 at 7:43 AM, Vik Fearing vik.fear...@dalibo.com wrote:
On 03/01/2014 07:50 PM, Josh Berkus wrote:
On 03/01/2014 09:01 AM, Peter Eisentraut wrote:
Status Summary. Needs Review: 36, Waiting on Author: 7, Ready for
Committer: 16, Committed: 43, Returned with Feedback: 8,
On Mon, Mar 3, 2014 at 1:13 PM, Andrew Dunstan and...@dunslane.net wrote:
That difference actually made the file_fdw regression results plain
wrong,
in my view, in that they expected a quoted empty string to be turned to
null
even when the null string was something else.
I've adjusted this
On Mon, Mar 3, 2014 at 9:06 PM, Robert Haas robertmh...@gmail.com wrote:
On Thu, Feb 27, 2014 at 8:12 AM, Michael Paquier
michael.paqu...@gmail.com wrote:
When working on the datatype pg_lsn, we actually did not create a
define macro for its oid in pg_type.h and this could be useful
On Wed, Mar 5, 2014 at 7:44 AM, Andrew Dunstan and...@dunslane.net wrote:
I have picked this up and committed the patch. Thanks to all.
Sorry for coming after the battle, but while looking at what has been
committed I noticed that copy2.sql is actually doing twice in a row
the same test:
COPY
After testing this feature, I noticed that FORCE_NULL and
FORCE_NOT_NULL can both be specified with COPY on the same column.
This does not seem correct. The attached patch adds some more error
handling, and a regression test case for that.
Regards,
--
Michael
diff --git
On Wed, Mar 5, 2014 at 11:37 PM, Ian Lawrence Barwick barw...@gmail.com wrote:
2014-03-05 23:27 GMT+09:00 Andrew Dunstan and...@dunslane.net:
On 03/05/2014 09:11 AM, Michael Paquier wrote:
After testing this feature, I noticed that FORCE_NULL and
FORCE_NOT_NULL can both be specified
On Wed, Mar 5, 2014 at 11:58 PM, Michael Paquier
michael.paqu...@gmail.com wrote:
So if we specify both this produces the exact opposite of the default,
default being an empty string inserted for a quoted empty string and
NULL inserted for a non-quoted empty string. So yes I'm fine with a
note
Hi all,
In the documentation, particularly the doc index, syslog_ident is
incorrectly mentioned as syslog_identify. The attached patch fixes
that. This error is in the docs since 8.0.
Regards,
--
Michael
*** a/doc/src/sgml/config.sgml
--- b/doc/src/sgml/config.sgml
***
*** 3743,3749
On Thu, Mar 6, 2014 at 12:09 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Andrew Dunstan and...@dunslane.net writes:
On 03/05/2014 09:11 AM, Michael Paquier wrote:
After testing this feature, I noticed that FORCE_NULL and
FORCE_NOT_NULL can both be specified with COPY on the same column.
Strictly
On Mon, Mar 10, 2014 at 2:09 PM, Robert Berry berrydigi...@gmail.com wrote:
Is there a way to get access to the StrategyControl pointer in the context
of a background worker?
StrategyControl is inherent to freelist.c and has no external
declaration so you could not have it even if you the
Hi all,
I have been playing a bit with the replication slots, and I noticed a
weird behavior in such a scenario:
1) Create a master/slave cluster, and have slave use a replication slot
2) Stop the master
3) Create a certain amount of WAL, during my tests I played with 4~5GB of WAL
4) Restart the
On Mon, Mar 10, 2014 at 9:24 PM, Andres Freund and...@2ndquadrant.com wrote:
Hi,
On 2014-03-10 21:06:53 +0900, Michael Paquier wrote:
I have been playing a bit with the replication slots, and I noticed a
weird behavior in such a scenario:
1) Create a master/slave cluster, and have slave use
On Thu, Mar 13, 2014 at 5:45 AM, Thom Brown t...@linux.com wrote:
On 12 March 2014 19:00, Josh Berkus j...@agliodbs.com wrote:
All:
I was just reading Michael's explanation of replication slots
(http://michael.otacoo.com/postgresql-2/postgres-9-4-feature-highlight-replication-slots/)
and
On Wed, Mar 12, 2014 at 11:16 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Julien Tachoires julien.tachoi...@dalibo.com writes:
A customer has reported us a strange behaviour regarding a rowtype
column with a domain subfield:
Rowtypes in general do not support defaults for component fields.
And
Hi,
I found a small typo in nbtree.h, introduced by commit efada2b. Patch
is attached.
Regards,
--
Michael
diff --git a/src/include/access/nbtree.h b/src/include/access/nbtree.h
index 7b26f98..779a422 100644
--- a/src/include/access/nbtree.h
+++ b/src/include/access/nbtree.h
@@ -395,7 +395,7 @@
On Tue, Mar 18, 2014 at 10:24 AM, Fabrízio de Royes Mello
fabriziome...@gmail.com wrote:
On Thu, Mar 13, 2014 at 10:22 AM, Robert Haas robertmh...@gmail.com wrote:
Well, it's fairly harmless, but it might not be a bad idea to tighten that
up.
The attached patch tighten that up.
Hm... It might
On Fri, Mar 21, 2014 at 8:54 PM, MauMau maumau...@gmail.com wrote:
* Create pg_copy in C so that it can be used on Windows as well as on
UNIX/Linux. It just copies one file. Its source code is located in
src/bin/pg_copy/. Please recommend a better name if you have one in mind.
I'd rather see
On Sat, Mar 22, 2014 at 12:56 AM, Emanuel Calvo
emanuel.ca...@2ndquadrant.com wrote:
I realized that the output of the CREATE RULE has not a detailed
output for the events parameter.
But the question here is that I'm not sure which format follow:
{ INSERT | UPDATE | DELETE | SELECT}
or
On Sat, Mar 22, 2014 at 11:18 AM, Jaime Casanova ja...@2ndquadrant.com wrote:
On Fri, Mar 21, 2014 at 8:15 PM, Michael Paquier
michael.paqu...@gmail.com wrote:
On Sat, Mar 22, 2014 at 12:56 AM, Emanuel Calvo
emanuel.ca...@2ndquadrant.com wrote:
I realized that the output of the CREATE RULE
On Mon, Mar 24, 2014 at 5:54 PM, Magnus Hagander mag...@hagander.net wrote:
I was looking at http://www.postgresql.org/docs/devel/static/bgworker.html
with a client today.
It says:
Unlike RegisterBackgroundWorker, which can only be called from within the
On Tue, Mar 25, 2014 at 2:44 AM, Tanmay Deshpande
tp.deshpand...@gmail.com wrote:
We are trying add columnar support to postgreSQL and for that we need
identify each column in each relation by an oid. So my doubt is how do we
add an attribute/ a column to catalog pg_attribute ?
You can identify
On Mon, Mar 24, 2014 at 11:03 PM, Magnus Hagander mag...@hagander.net wrote:
That's what I thought. Can a dynamic background worker start *another*
dynamic background worker, or can they only be started from first level
background workers?
I have never really tried by myself, but I don't see
Hi all,
The behavior of rollback when an error occurs on an handle is
controlled by extending Protocol with $PROTNUM-[0|1|2] where:
- 0 = let the application handle rollbacks
- 1 = rollback whole transaction when an error occurs
- 2 = rollback only statement that failed
Using such an extension is
On Wed, Mar 26, 2014 at 3:39 PM, Michael Paquier
michael.paqu...@gmail.com wrote:
Hi all,
The behavior of rollback when an error occurs on an handle is
controlled by extending Protocol with $PROTNUM-[0|1|2]...
My apologies. This message was sent to the wrong mailing list and was
dedicated
On Fri, Mar 28, 2014 at 4:10 AM, Peter Geoghegan p...@heroku.com wrote:
With the addition of LATERAL subqueries, Tom fixed up the mechanism
for keeping track of which relations are visible for column references
while the FROM clause is being scanned. That allowed
errorMissingColumn() to give a
On Mon, Mar 31, 2014 at 1:36 PM, Fabrízio de Royes Mello
fabriziome...@gmail.com wrote:
It's a nice idea, but the deadline to students send a proposal was 21th
April.
21st of March. All the details are here:
http://www.postgresql.org/developer/summerofcode/
--
Michael
--
Sent via
On Wed, Mar 26, 2014 at 5:53 PM, Heikki Linnakangas
hlinnakan...@vmware.com wrote:
* I'm not too fond of the RollbackError name. It sounds like an error while
rolling back. I googled around and found out that DataDirect's proprietary
driver has the same option, and they call it
On Mon, Mar 31, 2014 at 9:40 PM, Michael Paquier
michael.paqu...@gmail.com wrote:
OK, I have been working more on that, giving the attached patch...
Sorry, wrong mailing list...
My apologies.
--
Michael
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
On Tue, Apr 1, 2014 at 7:28 AM, Fabrízio de Royes Mello
fabriziome...@gmail.com wrote:
Think about the statements below:
CREATE ROLE test NOLOGIN;
CREATE OR REPLACE ROLE test;
If we execute the statements above the result should be the role 'test' can
login. Correct?
Except if I am missing
On Tue, Apr 1, 2014 at 1:33 AM, Alvaro Herrera alvhe...@2ndquadrant.com wrote:
steve k wrote:
I am examining other ways to do mass inserts/writes that allow for
notification if some of the data contained within for some reason fails to
copy/insert so that the cause of the bad data can be
On Tue, Apr 1, 2014 at 1:34 PM, Stephen Frost sfr...@snowman.net wrote:
* Michael Paquier (michael.paqu...@gmail.com) wrote:
On Tue, Apr 1, 2014 at 7:28 AM, Fabrízio de Royes Mello
fabriziome...@gmail.com wrote:
Think about the statements below:
CREATE ROLE test NOLOGIN;
CREATE
Hi all,
As of now, pg_basebackup creates an empty repository for pg_replslot/
in a base backup, forcing the user to recreate slots on other nodes of
the cluster with pg_create_*_replication_slot, or copy pg_replslot
from another node. This is not really user-friendly especially after a
failover
901 - 1000 of 5421 matches
Mail list logo
