On 27 July 2015 at 21:09, Kyotaro HORIGUCHI horiguchi.kyot...@lab.ntt.co.jp
wrote:
Hello, can I ask some questions?
I suppose we can take this as the analog of ParalleSeqScan. I
can see not so distinction between Append(ParalleSeqScan) and
ParallelAppend(SeqScan). What difference is there
On 23 July 2015 at 13:31, Rajeev rastogi rajeev.rast...@huawei.com wrote:
1.The autonomous transaction treated as a completely different
transaction from the master transaction.
Personally I think that's a lot more useful than having the inner tx
able to see the outer tx's
On Tue, Jul 28, 2015 at 12:59 PM, David Rowley david.row...@2ndquadrant.com
wrote:
On 27 July 2015 at 21:09, Kyotaro HORIGUCHI
horiguchi.kyot...@lab.ntt.co.jp wrote:
Hello, can I ask some questions?
I suppose we can take this as the analog of ParalleSeqScan. I
can see not so
2015-07-28 5:24 GMT+02:00 Pavel Stehule pavel.steh...@gmail.com:
2015-07-27 21:57 GMT+02:00 Andrew Dunstan and...@dunslane.net:
On 07/27/2015 02:53 PM, Pavel Stehule wrote:
I am trying to run parallel execution
psql -At -c select datname from pg_database
On Tue, Jul 28, 2015 at 12:56 AM, Josh Berkus j...@agliodbs.com wrote:
Ah, ok. The goal of the project is that the writer of X() *cannot*
prevent Y() from writing its data (B1) and committing it.
One of the primary use cases for ATX is audit triggers. If a function
writer could override
Attached fixes a minor typo:
s/custom/foreign/g
Thanks,
Amit
diff --git a/src/backend/optimizer/plan/setrefs.c b/src/backend/optimizer/plan/setrefs.c
index ea185d4..ee8710d 100644
--- a/src/backend/optimizer/plan/setrefs.c
+++ b/src/backend/optimizer/plan/setrefs.c
@@ -1099,7 +1099,7 @@
On 27.07.2015 22:09, Stephen Frost wrote:
* Egor Rogov (e.ro...@postgrespro.ru) wrote:
On Thu, Jul 23, 2015 at 8:30 AM, Egor Rogov e.ro...@postgrespro.ru wrote:
So, the question: is it a documentation bug (as it seems to me), code bug,
or I missed something?
Your analysis looks right to me,
Hi,
for something between 10% and 20% of the devel builds for apt.postgresql.org
(which happen every 6h if there's a git change, so it happens every few days),
I'm seeing this:
make[2]: Entering directory
'/tmp/buildd/postgresql-9.6-9.6~~devel~20150728.0405/build/src/bin/pg_rewind'
rm -rf
On 28 July 2015 at 03:19, Joe Conway m...@joeconway.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/27/2015 03:05 PM, Stephen Frost wrote:
AFK at the moment, but my thinking was that we should avoid having
the error message change based on what a GUC is set to. I agree
that
On 7/22/15 12:43 AM, Michael Paquier wrote:
OK, thanks for the updated versions. Those ones look good to me.
Committed, thanks.
Now, do we plan to do something about the creation of a slot. I
imagine that it would be useful if we could have --create-slot to
create a slot when beginning a
On 7/21/15 8:52 PM, Andreas Karlsson wrote:
It is not enough to just add a hook to the GUCs since I would guess most
users would expect the certificate to be reloaded if just the file has
been replaced and no GUC was changed. To support this we would need to
also check the mtimes of the SSL
Qingqing Zhou zhouqq.postg...@gmail.com writes:
There are still something bothering me: EXPLAIN is a mixed output with
original text, rows for RelOptInfo, rows for Paths and possible others
added later. So we have to use 't as text' to receive each line. To do the
insertion, we have to further
On 07/03/2015 10:03 AM, Noah Misch wrote:
(6) AlterPolicy() calls InvokeObjectPostAlterHook(PolicyRelationId, ...), but
CreatePolicy() and DropPolicy() lack their respective hook invocations.
Patch attached. Actually AlterPolicy() was also missing its hook -- the
existing
Michael Paquier michael.paqu...@gmail.com writes:
On Wed, Jul 29, 2015 at 5:22 AM, Heikki Linnakangas wrote:
On 07/28/2015 11:01 PM, Alvaro Herrera wrote:
Do we want to have this in src/test/modules or src/bin/pg_dump/t?
Are we testing pg_dump here, or are we testing extensions? If the
On 07/23/2015 07:19 AM, Michael Paquier wrote:
On Wed, Jul 22, 2015 at 9:52 AM, Andreas Karlsson andr...@proxel.se wrote:
On 07/02/2015 06:13 PM, Peter Eisentraut wrote:
I think this would be a useful feature, and the implementation looks
sound. But I don't like how the reload is
On 2015-07-29 AM 11:02, Kouhei Kaigai wrote:
...
synchronous Append path vs. parallel asynchronous Append with Funnel
(below/above?) it. I guess the asynchronous version would always be
cheaper. So, even if we end up with non-parallel sub-plans do we still add
a Funnel to make Append
On Mon, Jul 27, 2015 at 4:58 PM, Stephen Frost sfr...@snowman.net wrote:
I would expect that if the current user has permission to bypass RLS,
and they have set row_security to OFF, then it should be off for all
tables that they have access to, regardless of how they access those
tables
On 28-07-2015 15:35, Josh Berkus wrote:
pg_standby_is_streaming()
returns true if the standby is configured for streaming and
is currently connected with the master.
returns false if the connection to the master is broken,
of if there is no primary_conninfo
+1.
Peter Eisentraut pete...@gmx.net writes:
I don't have a problem with rebuilding the SSL context on every reload
cycle. We already do a lot of extra reloading every time, so a bit more
shouldn't hurt. But I'm not so sure whether we should do that in the
SIGHUP handler. I don't know how we
Hi,
Attached fixes a typo:
- * no permanent tables cannot reference unlogged ones.
+ * permanent tables cannot reference unlogged ones.
Thanks,
Amit
diff --git a/src/backend/commands/tablecmds.c b/src/backend/commands/tablecmds.c
index 1c7eded..b459b1e 100644
---
On 2015-07-29 09:37:26 +1200, David Rowley wrote:
On 29 July 2015 at 03:25, Andres Freund and...@anarazel.de wrote:
On 2015-07-29 03:10:41 +1200, David Rowley wrote:
Have you thought about what to do when HAVE_INT64_TIMESTAMP is not
defined?
I don't think it's actually important. The
Alvaro Herrera alvhe...@2ndquadrant.com writes:
Tom Lane wrote:
Bottom line is that somebody failed to consider the possibility of a
null comparison value reaching the BRIN index lookup machinery.
The code stanza that's failing supposes that only IS NULL or IS NOT NULL
tests could have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/27/2015 05:34 PM, Joe Conway wrote:
On 07/27/2015 01:13 PM, Alvaro Herrera wrote:
Hmm, these are not ACL objects, so conceptually it seems cleaner
to use a different symbol for this. I think the catalog state
and the error messages would be
On Tue, Jul 28, 2015 at 2:43 PM, Tom Lane t...@sss.pgh.pa.us wrote:
You can do something like that in plpgsql, for example
declare t text;
for t in EXPLAIN SELECT ...
loop
insert into whatever values(t);
end loop;
I see - this is cool.
There are still something
On 07/27/2015 12:15 PM, Andrew Dunstan wrote:
On 07/27/2015 10:06 AM, Tom Lane wrote:
I challenge anybody to figure out what happened here:
http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hornetdt=2015-07-27%2010%3A25%3A17
or here:
On 07/28/2015 08:58 PM, Tom Lane wrote:
Andrew Dunstan and...@dunslane.net writes:
On 07/27/2015 10:06 AM, Tom Lane wrote:
I think we should disable TAP testing in the buildfarm until there is
some credible form of error reporting for it.
The situation should now be substantially improved.
Andrew Dunstan and...@dunslane.net writes:
On 07/27/2015 10:06 AM, Tom Lane wrote:
I think we should disable TAP testing in the buildfarm until there is
some credible form of error reporting for it.
The situation should now be substantially improved.
Hm, I was just thinking we weren't there
On 2015-07-28 PM 09:58, Kouhei Kaigai wrote:
From my understanding of parallel seqscan patch, each worker's
PartialSeqScan asks for a block to scan using a shared parallel heap scan
descriptor that effectively keeps track of division of work among
PartialSeqScans in terms of blocks.
On Wed, Jul 29, 2015 at 10:24 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Peter Eisentraut pete...@gmx.net writes:
I don't have a problem with rebuilding the SSL context on every reload
cycle. We already do a lot of extra reloading every time, so a bit more
shouldn't hurt. But I'm not so sure
On 28 July 2015 15:31, Craig Ringer Wrote:
2.It should be allowed to deadlock with master transaction.
We
need to work-out a solution to avoid deadlock.
The deadlock case in autonomous tx's is a bit different.
Assuming you don't intend to allow interleaving, where you can switch
On Wed, Jul 29, 2015 at 5:22 AM, Heikki Linnakangas wrote:
On 07/28/2015 11:01 PM, Alvaro Herrera wrote:
Improving test coverage of extensions with pg_dump
Do we want to have this in src/test/modules or src/bin/pg_dump/t?
Are we testing pg_dump here, or are we testing extensions? If the
KaiGai-san,
On 2015-07-28 PM 09:58, Kouhei Kaigai wrote:
From my understanding of parallel seqscan patch, each worker's
PartialSeqScan asks for a block to scan using a shared parallel heap scan
descriptor that effectively keeps track of division of work among
PartialSeqScans in terms of
v6 is just a rebase after a bug fix by Andres Freund.
Also a small question: The patch currently displays pgbench scripts
starting numbering at 0. Probably a little too geek... should start at 1?
--
Fabien.diff --git a/doc/src/sgml/ref/pgbench.sgml b/doc/src/sgml/ref/pgbench.sgml
index
On 2015-07-28 10:59:15 +1200, David Rowley wrote:
It won't be quite as fast as what you've written, but I think it will be
much neater and more likely to be used in other places if we invent a
function like pg_ltoa() which returns a pointer to the new end of string.
Also if we're specifying
On Tue, Jul 28, 2015 at 5:57 PM, Christoph Berg m...@debian.org wrote:
for something between 10% and 20% of the devel builds for apt.postgresql.org
(which happen every 6h if there's a git change, so it happens every few days),
I'm seeing this:
Dubious, test returned 1 (wstat 256, 0x100)
On 07/28/2015 04:43 AM, Marc Mamin wrote:
2015-07-28 5:24 GMT+02:00 Pavel Stehule pavel.steh...@gmail.com:
2015-07-27 21:57 GMT+02:00 Andrew Dunstan and...@dunslane.net:
On 07/27/2015 02:53 PM, Pavel Stehule wrote:
I am trying to run parallel execution
On 07/28/2015 12:08 AM, Pavel Stehule wrote:
2015-07-28 5:24 GMT+02:00 Pavel Stehule pavel.steh...@gmail.com
mailto:pavel.steh...@gmail.com:
2015-07-27 21:57 GMT+02:00 Andrew Dunstan and...@dunslane.net
mailto:and...@dunslane.net:
On 07/27/2015 02:53 PM, Pavel Stehule
On 27 July 2015 at 21:09, Kyotaro HORIGUCHI horiguchi.kyot...@lab.ntt.co.jp
wrote:
Hello, can I ask some questions?
I suppose we can take this as the analog of ParalleSeqScan. I
can see not so distinction between Append(ParalleSeqScan) and
Qingqing Zhou wrote:
Attached is a draft patch implementing the idea. To play with it, you
shall create the follow two foreign tables:
CREATE EXTENSION file_fdw;
CREATE SERVER pglog FOREIGN DATA WRAPPER file_fdw;
create foreign table pg_planner_rels(rel text, content text)server
pglog
On Sat, Jul 25, 2015 at 4:11 AM, Simon Riggs si...@2ndquadrant.com wrote:
On 22 July 2015 at 21:45, Robert Haas robertmh...@gmail.com wrote:
But it seemed to me that this could be rather confusing. I thought it
would be better to be explicit about whether the protections are
enabled in all
Hi,
On 2015-07-19 11:49:14 -0700, Jeff Janes wrote:
After applying this patch to commit fdf28853ae6a397497b79f, it has survived
testing long enough to convince that this fixes the problem.
What was the actual workload breaking with the bug? I ran a small
variety and I couldn't reproduce it
On 28 July 2015 at 19:10, Andres Freund and...@anarazel.de wrote:
On 2015-07-28 10:59:15 +1200, David Rowley wrote:
It won't be quite as fast as what you've written, but I think it will be
much neater and more likely to be used in other places if we invent a
function like pg_ltoa() which
On 07/09/2015 06:29 AM, Heikki Linnakangas wrote:
On 07/09/2015 04:50 AM, Michael Paquier wrote:
Except that this patch looks good to me. Thanks for the black magic on
stdout/stderr handling.
Thanks, fixed the parenthesis and committed. The missing --debug is a
separate issue.
What
2015-07-28 15:16 GMT+02:00 Andrew Dunstan and...@dunslane.net:
On 07/28/2015 12:08 AM, Pavel Stehule wrote:
2015-07-28 5:24 GMT+02:00 Pavel Stehule pavel.steh...@gmail.com mailto:
pavel.steh...@gmail.com:
2015-07-27 21:57 GMT+02:00 Andrew Dunstan and...@dunslane.net
On Tue, Jul 28, 2015 at 7:06 AM, Andres Freund and...@anarazel.de wrote:
Hi,
On 2015-07-19 11:49:14 -0700, Jeff Janes wrote:
After applying this patch to commit fdf28853ae6a397497b79f, it has
survived
testing long enough to convince that this fixes the problem.
What was the actual
Heikki Linnakangas hlinn...@iki.fi writes:
On 07/28/2015 04:14 AM, David Rowley wrote:
I'd not thought of an input function being volatile before, but I guess
it's possible, which makes me a bit scared that we could be treading on
ground we shouldn't be. I know it's more of an output function
On 2015-07-29 03:10:41 +1200, David Rowley wrote:
timestamp_out() = 2015-07-29 02:24:33.34 in 3.506000
timestamp_out_old() = 2015-07-29 02:24:33.034 in 64.518000
timestamp_out_af() = 2015-07-29 02:24:33.034 in 2.981000
timestamp_out_old is master's version, the timestamp_out_af() is yours,
On 07/03/2015 10:03 AM, Noah Misch wrote:
(4) When DefineQueryRewrite() is about to convert a table to a view, it checks
the table for features unavailable to views. For example, it rejects tables
having triggers. It omits to reject tables having relrowsecurity or a
pg_policy record. Test
On 07/28/2015 04:14 AM, David Rowley wrote:
On 27 July 2015 at 20:11, Heikki Linnakangas hlinn...@iki.fi wrote:
On 07/27/2015 08:34 AM, David Rowley wrote:
In this function I also wasn't quite sure if it was with comparing both
non-NULL INITCOND's here. I believe my code comments may
2015-07-28 10:43 GMT+02:00 Marc Mamin m.ma...@intershop.de:
2015-07-28 5:24 GMT+02:00 Pavel Stehule pavel.steh...@gmail.com:
2015-07-27 21:57 GMT+02:00 Andrew Dunstan and...@dunslane.net:
On 07/27/2015 02:53 PM, Pavel Stehule wrote:
2015-07-28 10:43 GMT+02:00 Marc Mamin m.ma...@intershop.de:
2015-07-28 5:24 GMT+02:00 Pavel Stehule pavel.steh...@gmail.com:
2015-07-27 21:57 GMT+02:00 Andrew Dunstan and...@dunslane.net:
On 07/27/2015 02:53 PM, Pavel Stehule wrote:
I am trying to run
KaiGai-san,
On 2015-07-27 PM 11:07, Kouhei Kaigai wrote:
Append
-- Funnel
-- PartialSeqScan on rel1 (num_workers = 4)
-- Funnel
-- PartialSeqScan on rel2 (num_workers = 8)
-- SeqScan on rel3
shall be rewritten to
Funnel
-- PartialSeqScan
On 07/27/2015 03:52 AM, Marc Mamin wrote:
As per attached patch.
Comments?
It seems that the first test on the compression in pg_backup_tar.c is now
obsolete.
It didn't make much sense anyway.
211 if (AH-compression 0 || AH-compression 9)
212 AH-compression =
On 17 July 2015 at 03:42, Pavel Stehule pavel.steh...@gmail.com wrote:
Hi
can we support multiple -c option?
Why? Because some statements like VACUUM cannot be used together with any
other statements with single -c option. The current solution is using echo
and pipe op, but it is a
On Tue, Jul 28, 2015 at 7:59 AM, Kouhei Kaigai kai...@ak.jp.nec.com wrote:
-Original Message-
From: pgsql-hackers-ow...@postgresql.org
[mailto:pgsql-hackers-ow...@postgresql.org] On Behalf Of Kouhei Kaigai
Sent: Monday, July 27, 2015 11:07 PM
To: Amit Kapila
Is
2015-07-28 21:51 GMT+02:00 Heikki Linnakangas hlinn...@iki.fi:
21 patches remain in Needs Review state, in the July commitfest. Some of
them have a reviewer signed up. I have highlighted some of them below that
worry me the most. What are we going to do about these? For each of them,
I'd like
Hackers,
I am updating the list of PostgreSQL contributors.
Please help me with this by nominating the following, and sending me
*off-list* email:
* people who did several really good reviews for 9.4/9.5
* people who did useful testing for 9.4/9.5
* people who did other really helpful things
On Tue, Jul 28, 2015 at 03:36:13PM -0400, Robert Haas wrote:
On Tue, Jul 28, 2015 at 3:33 PM, Andres Freund and...@anarazel.de wrote:
Hm? Let me try again: If the admin does a ALTER DATABASE ... SET guc =
... *before* restoring a backup and the backup does contain a setting
for the same
On 07/03/2015 10:03 AM, Noah Misch wrote:
(7) Using an aggregate function in a policy predicate elicits an inapposite
error message due to use of EXPR_KIND_WHERE for parse analysis. Need a new
ParseExprKind. Test case:
Patch attached. Comments?
Joe
diff --git
Heikki Linnakangas hlinn...@iki.fi writes:
On 07/28/2015 07:18 PM, Tom Lane wrote:
Heikki Linnakangas hlinn...@iki.fi writes:
BTW, we're also not checking if the transition or final functions are
volatile. But that was the same before this patch too.
Up to now it hasn't mattered.
Yes, it
* Dean Rasheed (dean.a.rash...@gmail.com) wrote:
On 28 July 2015 at 03:19, Joe Conway m...@joeconway.com wrote:
On 07/27/2015 03:05 PM, Stephen Frost wrote:
AFK at the moment, but my thinking was that we should avoid having
the error message change based on what a GUC is set to. I agree
Qingqing Zhou wrote:
On Mon, Jul 27, 2015 at 8:20 PM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
I think this is a pretty neat idea, but I'm not sure this user interface
is a good one. Why not have a new option for EXPLAIN, so you would call
EXPLAIN (planner_stuff=on) and it returns
So, we have this patch in the commitfest again. Let's see where we are,
and try to find a consensus on what needs to be done before this can be
committed.
On 06/17/2015 06:51 PM, Petr Jelinek wrote:
On 2015-06-15 11:32, Vik Fearing wrote:
I've been looking at these patches a bit and here are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/28/2015 12:32 AM, Dean Rasheed wrote:
On 07/27/2015 03:05 PM, Stephen Frost wrote:
AFK at the moment, but my thinking was that we should avoid
having the error message change based on what a GUC is set to.
I agree that there should be
On 2015-07-28 11:35:52 -0700, Josh Berkus wrote:
Since merging recovery.conf with postgresql.conf is apparently off the
table indefinitely
Off the table as in somebody needs to actually work on it instead of
just talking about it.
--
Sent via pgsql-hackers mailing list
* Joe Conway (joe.con...@crunchydata.com) wrote:
On 07/03/2015 10:03 AM, Noah Misch wrote:
(4) When DefineQueryRewrite() is about to convert a table to a view, it
checks
the table for features unavailable to views. For example, it rejects tables
having triggers. It omits to reject
* Robert Haas (robertmh...@gmail.com) wrote:
On Sun, Jul 26, 2015 at 11:43 PM, Craig Ringer cr...@2ndquadrant.com wrote:
On 20 July 2015 at 01:18, Noah Misch n...@leadboat.com wrote:
On Wed, Jul 15, 2015 at 11:08:53AM +0200, Andres Freund wrote:
On 2015-07-15 12:04:40 +0300, Alvaro Herrera
On Mon, Jul 27, 2015 at 8:20 PM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
I think this is a pretty neat idea, but I'm not sure this user interface
is a good one. Why not have a new option for EXPLAIN, so you would call
EXPLAIN (planner_stuff=on) and it returns this as a resultset?
Hackers,
Since merging recovery.conf with postgresql.conf is apparently off the
table indefinitely, we could really use some additional information
functions which work on the replica. Here's my list of what I need for
failover automation:
pg_standby_is_streaming()
returns true if the
Tom Lane wrote:
Bottom line is that somebody failed to consider the possibility of a
null comparison value reaching the BRIN index lookup machinery.
The code stanza that's failing supposes that only IS NULL or IS NOT NULL
tests could have SK_ISNULL set, but that's just wrong.
I think the
On 2015-07-28 20:11, Heikki Linnakangas wrote:
Petr, is this enough feedback on this patch for this commitfest, or are
there some other issues you want to discuss before I mark this as returned?
You can mark it as returned, I didn't have much time to actually do much
useful work on this in
On Wed, Nov 5, 2014 at 9:26 PM, Robert Haas robertmh...@gmail.com wrote:
On Sun, Nov 2, 2014 at 7:31 AM, Simon Riggs si...@2ndquadrant.com wrote:
The procgloballist stuff should be the subject of a separate patch
which I agree with.
Yes, I think that's probably a net improvement in robustness
On Sun, Jul 26, 2015 at 11:43 PM, Craig Ringer cr...@2ndquadrant.com wrote:
On 20 July 2015 at 01:18, Noah Misch n...@leadboat.com wrote:
On Wed, Jul 15, 2015 at 11:08:53AM +0200, Andres Freund wrote:
On 2015-07-15 12:04:40 +0300, Alvaro Herrera wrote:
Andres Freund wrote:
One thing worth
On 2015-07-28 14:58:26 -0400, Robert Haas wrote:
Yes, I think we should make restoring the database's properties the
job of pg_dump and remove it completely from pg_dumpall, unless we can
find a case where that's really going to break things.
CREATE DATABASE blarg;
SECURITY LABEL ON blarg IS
I had a discussion with some folks at Red Hat about this:
https://bugzilla.redhat.com/show_bug.cgi?id=1247477
I had the idea that we had documented somewhere that the data directory
should not be a filesystem mount point, but I sure can't find it now.
Any objections to adding some text about this
On Tue, Jul 28, 2015 at 3:03 PM, Andres Freund and...@anarazel.de wrote:
On 2015-07-28 14:58:26 -0400, Robert Haas wrote:
Yes, I think we should make restoring the database's properties the
job of pg_dump and remove it completely from pg_dumpall, unless we can
find a case where that's really
On 2015-07-28 15:05:01 -0400, Robert Haas wrote:
On Tue, Jul 28, 2015 at 3:03 PM, Andres Freund and...@anarazel.de wrote:
On 2015-07-28 14:58:26 -0400, Robert Haas wrote:
Yes, I think we should make restoring the database's properties the
job of pg_dump and remove it completely from
On Tue, Jul 28, 2015 at 3:10 PM, Andres Freund and...@anarazel.de wrote:
On 2015-07-28 15:05:01 -0400, Robert Haas wrote:
On Tue, Jul 28, 2015 at 3:03 PM, Andres Freund and...@anarazel.de wrote:
On 2015-07-28 14:58:26 -0400, Robert Haas wrote:
Yes, I think we should make restoring the
Josh Berkus wrote:
On 07/28/2015 11:58 AM, Robert Haas wrote:
I'd be strongly in favour of teaching GRANT, SECURITY LABEL, COMMENT
ON DATABASE, etc to recognise CURRENT_DATABASE as a keyword. Then
dumping them in pg_dump --create, and in pg_dump -Fc .
In practice I see zero real use of
21 patches remain in Needs Review state, in the July commitfest. Some of
them have a reviewer signed up. I have highlighted some of them below
that worry me the most. What are we going to do about these? For each of
them, I'd like the authors to have some idea on what they need to do to
get
On 07/28/2015 12:51 PM, Heikki Linnakangas wrote:
Everyone wants the feature, using multi-line SELECTs in pgbench scripts,
but we don't seem to be reaching a consensus on how it should work. I
think we'll need to integrate the lexer, but it would be nice to still
support multi-statements as
On 2015-07-28 22:51:55 +0300, Heikki Linnakangas wrote:
checkpoint continuous flushing
This does a big memory allocation at checkpoint, which Tom vehemently
objects to.
Uh. Didn't he just object to failing in that case? IIRC he even
indicated tentative assent, a year or so back, with my idea
On 2015-07-28 15:14:11 -0400, Robert Haas wrote:
On Tue, Jul 28, 2015 at 3:10 PM, Andres Freund and...@anarazel.de wrote:
DBA creates a database and sets some properties (security labels, gucs,
acls) on it. Then goes on to restore a backup. Unfortunately that backup
might, or might not,
* Andres Freund (and...@anarazel.de) wrote:
On 2015-07-28 15:14:11 -0400, Robert Haas wrote:
On Tue, Jul 28, 2015 at 3:10 PM, Andres Freund and...@anarazel.de wrote:
DBA creates a database and sets some properties (security labels, gucs,
acls) on it. Then goes on to restore a backup.
On 28 Jul 2015, at 21:35, Josh Berkus j...@agliodbs.com wrote:
Hackers,
Since merging recovery.conf with postgresql.conf is apparently off the
table indefinitely, we could really use some additional information
functions which work on the replica. Here's my list of what I need for
On 07/27/2015 01:20 PM, Ildus Kurbangaliev wrote:
Hello.
In the attached patch I've made a refactoring for tranches.
The prefix for them was extended, and I've did a split of LWLockAssign
to two
functions (one with tranche and second for user defined LWLocks).
This needs some work in order to
On Tue, Jul 28, 2015 at 3:33 PM, Andres Freund and...@anarazel.de wrote:
On 2015-07-28 15:27:51 -0400, Robert Haas wrote:
On Tue, Jul 28, 2015 at 3:16 PM, Andres Freund and...@anarazel.de wrote:
On 2015-07-28 15:14:11 -0400, Robert Haas wrote:
On Tue, Jul 28, 2015 at 3:10 PM, Andres Freund
Alvaro Herrera alvhe...@2ndquadrant.com writes:
Qingqing Zhou wrote:
The file name is not random, it is fixed so we can create foreign table
once and use it afterwards - I actually want to push them into
system_views.sql.
Got that. That seems fragile and not very convenient; I don't think
Heikki Linnakangas wrote:
21 patches remain in Needs Review state, in the July commitfest. Some of
them have a reviewer signed up. I have highlighted some of them below that
worry me the most. What are we going to do about these? For each of them,
I'd like the authors to have some idea on what
On 2015-07-28 18:59:02 +0200, Andres Freund wrote:
Unless somebody protests soon I'm going to push something like that
after having dinner.
Done.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
On 07/28/2015 11:58 AM, Robert Haas wrote:
I'd be strongly in favour of teaching GRANT, SECURITY LABEL, COMMENT
ON DATABASE, etc to recognise CURRENT_DATABASE as a keyword. Then
dumping them in pg_dump --create, and in pg_dump -Fc .
In practice I see zero real use of pg_dumpall without
On Tue, Jul 28, 2015 at 3:16 PM, Andres Freund and...@anarazel.de wrote:
On 2015-07-28 15:14:11 -0400, Robert Haas wrote:
On Tue, Jul 28, 2015 at 3:10 PM, Andres Freund and...@anarazel.de wrote:
DBA creates a database and sets some properties (security labels, gucs,
acls) on it. Then goes on
On 2015-07-28 15:27:51 -0400, Robert Haas wrote:
On Tue, Jul 28, 2015 at 3:16 PM, Andres Freund and...@anarazel.de wrote:
On 2015-07-28 15:14:11 -0400, Robert Haas wrote:
On Tue, Jul 28, 2015 at 3:10 PM, Andres Freund and...@anarazel.de wrote:
DBA creates a database and sets some
Andres Freund wrote:
On 2015-07-28 18:59:02 +0200, Andres Freund wrote:
Unless somebody protests soon I'm going to push something like that
after having dinner.
Done.
Yay!
--
Álvaro Herrerahttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA,
Ah, you're missing how commits in ATX are expected to work. Let me
illustrate:
X (
Data write A1
call Y(
Start ATX
Data write B1
Commit ATX
)
Data write A2
Exception
)
In this workflow, B1 would be committed and persistent. Neither A1 nor
A2
On Tue, Jul 28, 2015 at 12:08 PM, Alvaro Herrera
alvhe...@2ndquadrant.com wrote:
I would have a tuplestore, and the planner code would push tuples to it.
After the planning is done, EXPLAIN can read and return tuples from the
store to the user.
Not sure if I got it: so EXPLAIN will return
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/28/2015 11:50 AM, Stephen Frost wrote:
* Joe Conway (joe.con...@crunchydata.com) wrote:
On 07/03/2015 10:03 AM, Noah Misch wrote:
(4) When DefineQueryRewrite() is about to convert a table to a
view, it checks the table for features
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/28/2015 11:17 AM, Joe Conway wrote:
I'm going to commit the attached in the next few hours unless
someone has serious objections. We can always revisit the specific
behavior of those messages separately if we change our minds...
Pushed to
On 28 July 2015 at 20:51, Heikki Linnakangas hlinn...@iki.fi wrote:
multivariate statistics
This has been a long discussion. Are we getting close to a committable
state?
This is important, but big.
COPY RAW
No consensus on whether to add this to the server's COPY command, or as a
On 07/28/2015 11:30 PM, Simon Riggs wrote:
I've added my name as committer to a few things, but won't be able to work
on them until at least next week when I've finished 9.5 stuff. Happy to
step back if anyone else wants to claim those.
Thanks, every little helps!
- Heikki
--
Sent via
1 - 100 of 108 matches
Mail list logo
