On Tue, Jul 7, 2015 at 12:57 PM, Fujii Masao masao.fu...@gmail.com wrote:
On Tue, Jun 30, 2015 at 10:30 PM, Amit Kapila amit.kapil...@gmail.com
wrote:
I have still not added documentation and have not changed anything for
waiting column in pg_stat_activity as I think before that we need to
Hi,
I had some trouble today with a misbehaving logical replication client
which had confirmed a flush of an LSN far into the future. Debugging it
was a bit of a pain for a number of reasons, but I think the most
important one was that confirmed_flush isn't exposed in
On Wed, Jul 8, 2015 at 1:35 AM, Pavel Stehule pavel.steh...@gmail.com wrote:
2015-07-07 18:15 GMT+02:00 Merlin Moncure mmonc...@gmail.com:
On Tue, Jul 7, 2015 at 9:04 AM, Pavel Stehule pavel.steh...@gmail.com
wrote:
It doesn't have to if the behavior is guarded with a GUC. I just
don't
On 2015-07-08 14:57, I wrote:
Adding this one to the next commit fest, but any feedback welcome in the
meanwhile.
Forgot to change PG_GET_REPLICATION_SLOTS_COLS; fixed in the attached patch.
.m
diff --git a/src/backend/catalog/system_views.sql
b/src/backend/catalog/system_views.sql
index
07.07.2015, 18:34, Michael Paquier michael.paqu...@gmail.com:
Speaking of which, I have rewritten the patch as attached. This looks
way cleaner than the previous version submitted. Dmitry, does that
look fine for you?
I am switching this patch as Waiting on Author.
Regards,
--
Hi
2015-07-08 9:08 GMT+02:00 Zhaomo Yang zhy...@cs.ucsd.edu:
more global temp tables are little bit comfortable for developers,
I'd like to emphasize this point. This feature does much more than saving
a developer from issuing a CREATE TEMP TABLE statement in every session.
Here are two
06.07.2015, 20:28, "Guillaume Lelarge" guilla...@lelarge.info: That sounds a lot like a background worker.Thank a lot! That's exactly what I was looking for. 07.07.2015, 03:29, "Jim Nasby" jim.na...@bluetreble.com: There is support for plugging into the parser and executor, so that might be a
On Wed, Jul 8, 2015 at 6:10 AM, Heikki Linnakangas hlinn...@iki.fi wrote:
On 06/25/2015 07:14 AM, Michael Paquier wrote:
After looking at the issues with the TAP test suite that hamster faced
a couple of days ago, which is what has been discussed on this thread:
Hi,
One of the debug messages related to logical replication could be more
helpful than it currently is. The attached patch reorders the two
operations to make it so.
Please consider patching and back-patching.
.m
diff --git a/src/backend/replication/logical/logical.c
On 03/21/2015 01:06 AM, Max Filippov wrote:
On Fri, Mar 20, 2015 at 3:43 PM, Max Filippov jcmvb...@gmail.com wrote:
Ok, one more attempt: maybe instead of checking that stderr is empty
we could check that stderr has changed in the presence of the option
that we test?
The patch:
Le 07/07/2015 14:55, Andres Freund a écrit :
On 2015-06-19 17:21:25 +0200, Cédric Villemain wrote:
To make slot usage in pg_receivexlog easier, should we add
--create-slot-if-not-exists? That'd mean you could run the same command
the first and later invocation.
+1 (with a shorter name
On 2015-07-08 14:11:59 +0900, Michael Paquier wrote:
Arg... I thought I triggered a couple of weeks a problem in this code
path when desc-arg_arraytype[i] is InvalidOid with argtypes == NULL.
Visibly I did something wrong...
Speaking of which, shouldn't this thing at least use OidIsValid?
-
Heikki Linnakangas hlinn...@iki.fi writes:
I suggest that we revert that work-around for that GCC bug, and stop
testing the pthread flags as soon as we find one that works.
OK ...
Then we can
also remove the test for whether the compiler produces any warnings.
Don't see how that follows?
On Tue, Jul 7, 2015 at 5:37 PM, Simon Riggs si...@2ndquadrant.com wrote:
On 6 July 2015 at 17:28, Simon Riggs si...@2ndquadrant.com wrote:
I think we need something for pg_upgrade to rewrite existing VMs.
Otherwise a large read only database would suddenly require a massive
revacuum after
2015-07-02 11:03 GMT+02:00 Heikki Linnakangas hlinn...@iki.fi:
On 05/29/2015 10:41 AM, Pavel Stehule wrote:
2015-05-29 9:28 GMT+02:00 Jeevan Chalke jeevan.cha...@gmail.com:
I agree with Peter that We don't tab-complete everything we possibly
could, but using tabs after SET ROLE TO
On Wed, Jul 8, 2015 at 9:15 PM, Дмитрий Воронин
carriingfat...@yandex.ru wrote:
07.07.2015, 18:34, Michael Paquier michael.paqu...@gmail.com:
Speaking of which, I have rewritten the patch as attached. This looks
way cleaner than the previous version submitted. Dmitry, does that
look fine
On Wed, Jul 8, 2015 at 3:20 AM, Ashutosh Bapat
ashutosh.ba...@enterprisedb.com wrote:
My intention for the 6th step is all recorded to wal, so if a crash
occurs the recovery process clean the mess.
AFAIU, PostgreSQL recovery is based on redoing WAL. What you described
earlier, undoing based
more global temp tables are little bit comfortable for developers,
I'd like to emphasize this point. This feature does much more than saving a
developer from issuing a CREATE TEMP TABLE statement in every session. Here
are two common use cases and I'm sure there are more.
(1)
Imagine in a web
On 7 July 2015 at 18:45, Sawada Masahiko sawada.m...@gmail.com wrote:
On Wed, Jul 8, 2015 at 12:37 AM, Andres Freund and...@anarazel.de wrote:
On 2015-07-07 16:25:13 +0100, Simon Riggs wrote:
I don't think pg_freespacemap is the right place.
I agree that pg_freespacemap sounds like an
On 2015-07-03 08:18:09 -0300, Fabrízio de Royes Mello wrote:
*** ALTER TABLE changes
...
Without going into the specifics of this change: Are we actually sure
this feature warrants the complexity it'll introduce? I'm really rather
doubtful.
--
Sent via pgsql-hackers mailing list
On 04/19/2015 11:18 AM, Mikko Tiihonen wrote:
Hi,
I would like allow specifying multiple host names for libpq to try to
connecting to. This is currently only supported if the host name
resolves to multiple addresses. Having the support for it without
complex dns setup would be much easier.
On Wed, Jul 8, 2015 at 10:53 AM, Andres Freund and...@anarazel.de wrote:
On 2015-07-03 08:18:09 -0300, Fabrízio de Royes Mello wrote:
*** ALTER TABLE changes
...
Without going into the specifics of this change: Are we actually sure
this feature warrants the complexity it'll introduce? I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/07/2015 10:22 PM, Michael Paquier wrote:
On Mon, Jul 6, 2015 at 11:52 PM, Joe Conway m...@joeconway.com
wrote:
That explains why the first example works while the second does
not. I'm not sure how hard it would be to fix that, but it
On Wed, Jul 8, 2015 at 10:12 AM, Joe Conway m...@joeconway.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/07/2015 10:22 PM, Michael Paquier wrote:
On Mon, Jul 6, 2015 at 11:52 PM, Joe Conway m...@joeconway.com
wrote:
That explains why the first example works while the second
On 2015-07-08 10:58:51 -0300, Fabrízio de Royes Mello wrote:
Think in an ETL job that can be use an unlogged table to improve the load
performance, but this job create a large table and to guarantee the data
consistency you need to transform it into a regular table, and with the
current
Noah,
* Noah Misch (n...@leadboat.com) wrote:
On Tue, Dec 02, 2014 at 11:32:27AM -0500, Stephen Frost wrote:
* Robert Haas (robertmh...@gmail.com) wrote:
On Thu, Nov 27, 2014 at 2:03 AM, Stephen Frost sfr...@snowman.net wrote:
Alright, I've done the change to use the RangeVar from
2015-07-08 17:12 GMT+02:00 Joe Conway m...@joeconway.com:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/07/2015 10:22 PM, Michael Paquier wrote:
On Mon, Jul 6, 2015 at 11:52 PM, Joe Conway m...@joeconway.com
wrote:
That explains why the first example works while the second does
Steve Singer st...@ssinger.info writes:
On 04/19/2015 11:18 AM, Mikko Tiihonen wrote:
Hi,
I would like allow specifying multiple host names for libpq to try to
connecting to. This is currently only supported if the host name
resolves to multiple addresses. Having the support for it
On 07/08/2015 11:26 AM, Michael Paquier wrote:
On Wed, Jul 8, 2015 at 6:10 AM, Heikki Linnakangas hlinn...@iki.fi wrote:
* whenever a test case is reported as success/fail.
Just to be sure, does this concern the ok/not ok messages printed
out by each test run? Or is it a custom message that
Hello.
Currently, PostgreSQL offers many metrics for monitoring. However, detailed
monitoring of waits is still not supported yet. Such monitoring would
let dba know how long backend waited for particular event and therefore
identify
bottlenecks. This functionality is very useful, especially
On 7/4/15 12:33 AM, Tom Lane wrote:
Jim Nasby jim.na...@bluetreble.com writes:
On 7/3/15 2:33 AM, Heikki Linnakangas wrote:
On 07/03/2015 01:20 AM, Jim Nasby wrote:
Is there a way to determine the operator that resulted in
calling the operator function? I thought
fcinfo-flinfo-fn_expr might
On Wed, Jul 8, 2015 at 11:29 AM, Merlin Moncure mmonc...@gmail.com wrote:
On Wed, Jul 8, 2015 at 10:12 AM, Joe Conway m...@joeconway.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/07/2015 10:22 PM, Michael Paquier wrote:
On Mon, Jul 6, 2015 at 11:52 PM, Joe Conway
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/08/2015 08:51 AM, Corey Huinker wrote:
Questions: Would moving rowtype to the first parameter resolve the
parameter ambiguity issue?
Not for the existing functions but with new functions I don't think it
matters. You would know to always
On 07/08/2015 04:38 PM, Tom Lane wrote:
Heikki Linnakangas hlinn...@iki.fi writes:
I suggest that we revert that work-around for that GCC bug, and stop
testing the pthread flags as soon as we find one that works.
OK ...
Then we can
also remove the test for whether the compiler produces any
Heikki Linnakangas hlinn...@iki.fi writes:
The only scenario where you might now get warnings if we switch to
upstream version, and didn't before, is if one of the flags makes
pthreads to work, but also creates compiler warnings, while another flag
later in the list would make it work
In dataPlaceToPageLeaf-function:
if (append)
{
/*
* Even when appending, trying to append more items than will
fit is
* not completely free, because we will merge the new items and
old
* items into an array
On Wed, Jul 8, 2015 at 4:39 PM, Pavel Stehule pavel.steh...@gmail.com wrote:
2015-07-08 8:35 GMT+02:00 Pavel Stehule pavel.steh...@gmail.com:
2015-07-07 18:15 GMT+02:00 Merlin Moncure mmonc...@gmail.com:
On Tue, Jul 7, 2015 at 9:04 AM, Pavel Stehule pavel.steh...@gmail.com
wrote:
It
Paul Ramsey pram...@cleverelephant.ca writes:
On Fri, Apr 25, 2014 at 4:54 PM, Peter Geoghegan p...@heroku.com wrote:
On Fri, Apr 25, 2014 at 4:47 PM, Paul Ramsey pram...@cleverelephant.ca
wrote:
Is it possible to make custom types hashable? There's no hook in the
CREATE TYPE call for a hash
On July 8, 2015 at 1:36:49 PM, Tom Lane (t...@sss.pgh.pa.us) wrote:
Paul Ramsey pram...@cleverelephant.ca writes:
UNION will preferentially glom onto the btree equality operator, if memory
serves. If that isn't also the hash equality operator, things won't work
pleasantly.
So… what
2015-07-08 8:35 GMT+02:00 Pavel Stehule pavel.steh...@gmail.com:
2015-07-07 18:15 GMT+02:00 Merlin Moncure mmonc...@gmail.com:
On Tue, Jul 7, 2015 at 9:04 AM, Pavel Stehule pavel.steh...@gmail.com
wrote:
It doesn't have to if the behavior is guarded with a GUC. I just
don't understand
2015-07-08 23:46 GMT+02:00 Merlin Moncure mmonc...@gmail.com:
On Wed, Jul 8, 2015 at 4:39 PM, Pavel Stehule pavel.steh...@gmail.com
wrote:
2015-07-08 8:35 GMT+02:00 Pavel Stehule pavel.steh...@gmail.com:
2015-07-07 18:15 GMT+02:00 Merlin Moncure mmonc...@gmail.com:
On Tue, Jul 7,
On Fri, Jul 3, 2015 at 1:25 AM, Sawada Masahiko sawada.m...@gmail.com
wrote:
On Fri, Jul 3, 2015 at 1:23 AM, Simon Riggs si...@2ndquadrant.com wrote:
On 2 July 2015 at 16:30, Sawada Masahiko sawada.m...@gmail.com wrote:
Also, the flags of each heap page header might be set PD_ALL_FROZEN,
Paul Ramsey pram...@cleverelephant.ca writes:
UNION will preferentially glom onto the btree equality operator, if memory
serves. If that isn't also the hash equality operator, things won't work
pleasantly.
So⦠what does that mean for types that have both btree and hash equality
It still says I lack the secret sauce...
ERROR: could not implement recursive UNION
DETAIL: All column datatypes must be hashable.
UNION will preferentially glom onto the btree equality operator, if memory
serves. If that isn't also the hash equality operator, things won't work
My Salesforce colleagues observed a failure mode in which a bug in the
crash recovery logic caused the startup process to get a SEGV while trying
to recover after a backend crash. The postmaster should have given up at
that point, but instead it kept on respawning the startup process, which
of
On Wed, Jul 8, 2015 at 1:27 AM, Fabrízio de Royes Mello
fabriziome...@gmail.com wrote:
On Fri, Jul 3, 2015 at 9:29 AM, Ashutosh Bapat
ashutosh.ba...@enterprisedb.com wrote:
On Fri, Jul 3, 2015 at 4:48 PM, Fabrízio de Royes Mello
fabriziome...@gmail.com wrote:
On Thu, Apr 2,
2015-07-07 18:15 GMT+02:00 Merlin Moncure mmonc...@gmail.com:
On Tue, Jul 7, 2015 at 9:04 AM, Pavel Stehule pavel.steh...@gmail.com
wrote:
It doesn't have to if the behavior is guarded with a GUC. I just
don't understand what all the fuss is about. The default behavior of
logging that
On Fri, Apr 25, 2014 at 4:54 PM, Peter Geoghegan p...@heroku.com wrote:
On Fri, Apr 25, 2014 at 4:47 PM, Paul Ramsey pram...@cleverelephant.ca
wrote:
Is it possible to make custom types hashable? There's no hook in the
CREATE TYPE call for a hash function, but can one be hooked up
somewhere
Hi
the comment about NOTICE level in elog.h is obsolete
Regards
Pavel
diff --git a/src/include/utils/elog.h b/src/include/utils/elog.h
new file mode 100644
index 8e90661..7684717
*** a/src/include/utils/elog.h
--- b/src/include/utils/elog.h
***
*** 33,40
* client
On Thu, Jul 9, 2015 at 1:52 AM, Ildus Kurbangaliev
i.kurbangal...@postgrespro.ru wrote:
Hello.
Currently, PostgreSQL offers many metrics for monitoring. However, detailed
monitoring of waits is still not supported yet. Such monitoring would
let dba know how long backend waited for particular
On 7 July 2015 at 20:23, David Rowley david.row...@2ndquadrant.com wrote:
On 7 July 2015 at 18:59, Jeff Davis pg...@j-davis.com wrote:
One other thing that I don't remember seeing discussed would be to
just store a List in each context which would store all of the
mem_allocated's that
Hi,
I just found that Log_disconnections value has not been
exposed to outside of postgres.c.
Despite that, Log_connections has already been exposed.
So, I'd like to add attached fix to touch the Log_disconnections
value in other modules.
Any comments?
Regards,
--
NAGAYASU Satoshi
On 2015/07/09 13:06, Tom Lane wrote:
Satoshi Nagayasu sn...@uptime.jp writes:
I just found that Log_disconnections value has not been
exposed to outside of postgres.c.
Despite that, Log_connections has already been exposed.
Why would an external module need to touch either one?
To check
On Sat, Jun 27, 2015 at 11:57:30AM -0700, Peter Geoghegan wrote:
On Sat, Jun 27, 2015 at 9:51 AM, Noah Misch n...@leadboat.com wrote:
PostgreSQL 9.5 adds a strxfrm() call in bttext_abbrev_convert(), which does
not account for the Solaris bug. I wish to determine whether that bug is
still
Satoshi Nagayasu sn...@uptime.jp writes:
I just found that Log_disconnections value has not been
exposed to outside of postgres.c.
Despite that, Log_connections has already been exposed.
Why would an external module need to touch either one?
regards, tom lane
--
On Mon, Jun 29, 2015 at 3:54 PM, Jeff Janes jeff.ja...@gmail.com wrote:
Attached is a patch that implements the vm scan for truncation. It
introduces a variable to hold the last blkno which was skipped during the
forward portion. Any blocks after both this blkno and after the last
inspected
On Thu, Jul 9, 2015 at 4:31 AM, Jeff Janes jeff.ja...@gmail.com wrote:
On Fri, Jul 3, 2015 at 1:25 AM, Sawada Masahiko sawada.m...@gmail.com
wrote:
On Fri, Jul 3, 2015 at 1:23 AM, Simon Riggs si...@2ndquadrant.com wrote:
On 2 July 2015 at 16:30, Sawada Masahiko sawada.m...@gmail.com wrote:
Attached find patch that makes certain comments in
predicate_refuted_by_recurse() clearer, for example:
-* AND-clause R= AND-clause if A refutes any of B's items
+* AND-clause A R= AND-clause B if A refutes any of B's items
The comment above the function is written using the
Hi
here is initial version of reduced patch. It is small code, but relative
big (although I expected bigger) change in tests.
if these changes are too big, then we have to introduce a plpgsql GUC
plpgsql.client_min_context and plpgsql.log_min_client. These GUC overwrite
global setting for
2015-07-09 7:32 GMT+02:00 Zhaomo Yang zhy...@cs.ucsd.edu:
I am not sure, if it is not useless work.
I don't understand why an implementation taking approach 2.a would be
useless. As I said, its performance will be no worse than current temp
tables and it will provide a lot of convenience
On Wed, Jul 08, 2015 at 10:55:47AM -0400, Stephen Frost wrote:
It's interesting to consider that COPY purportedly operates under the
SELECT privilege, yet fails to respect on-select rules.
In released branches, COPY consistently refuses to operate directly on a view.
(There's no (longer?) such
61 matches
Mail list logo
