> If I would make a proof-of-concept patch with interface itself, it
> seems to me file_fdw may be a good candidate for this enhancement.
> It is not a field for postgres_fdw.
>
The attached patch is enhancement of FDW/CSP interface and PoC feature
of file_fdw to scan source file partially. It was
On Thu, Jan 28, 2016 at 7:48 AM, Vladimir Sitnikov <
sitnikov.vladi...@gmail.com> wrote:
> Robert>Hmm, so in your example, you actually want replanning to be able to
> Robert>change the cached plan's result type?
>
> I want backend to cache _several_ plans behind a single "statement name".
> I
On Thu, Jan 28, 2016 at 10:25 AM, Stefan Kaltenbrunner
wrote:
> On 01/28/2016 04:00 PM, Stefan Kaltenbrunner wrote:
>> Per discussion in the afternoon break at FOSDEM/PGDay 2016 Developer
>> Meeting we are going to upgrade gemulon.postgresql.org aka "gitmaster"
>> today
On Thu, Jan 28, 2016 at 9:03 AM, Thom Brown wrote:
> I'm surprised that efficiencies can't be realised beyond this point. Your
> results show a sweet spot at around 1000 / 1000, with it getting slightly
> worse beyond that. I kind of expected a lot of efficiency where all
On Wed, Jan 27, 2016 at 6:32 AM, Ashutosh Bapat
wrote:
> As discussed in postgres_fdw join pushdown thread [1], for two different
> effective local users which use public user mapping we will be creating two
> different connections to the foreign server with the
On Thu, Jan 28, 2016 at 03:52:25PM +0100, Tom Lane wrote:
> Robert Haas writes:
> > On Thu, Jan 28, 2016 at 8:04 AM, Tomas Vondra
> > wrote:
> >> Why can't we do both? That is, have a free-form text with the nuances, and
> >> then Reviewed-By
* Robert Haas (robertmh...@gmail.com) wrote:
> On Sun, Jan 17, 2016 at 6:58 PM, Stephen Frost wrote:
> > I'm not against that idea, though I continue to feel that there are
> > common sets of privileges which backup tools could leverage.
> >
> > The other issue that I'm
On Thu, Jan 28, 2016 at 10:40:09AM -0500, Stephen Frost wrote:
> * Joshua D. Drake (j...@commandprompt.com) wrote:
> > On 01/28/2016 06:57 AM, Robert Haas wrote:
> >
> > >>I'm on board with Bruce's template as being a checklist of points to be
> > >>sure to cover when composing a commit message.
On 01/28/2016 05:24 PM, Robert Haas wrote:
> On Thu, Jan 28, 2016 at 10:25 AM, Stefan Kaltenbrunner
> wrote:
>> On 01/28/2016 04:00 PM, Stefan Kaltenbrunner wrote:
>>> Per discussion in the afternoon break at FOSDEM/PGDay 2016 Developer
>>> Meeting we are going to
On Thu, Jan 28, 2016 at 10:50 AM, Kouhei Kaigai wrote:
>> If I would make a proof-of-concept patch with interface itself, it
>> seems to me file_fdw may be a good candidate for this enhancement.
>> It is not a field for postgres_fdw.
>>
> The attached patch is enhancement of
So I'm arguing that exiting, with an error message, is better than handling
user errors.
I'm not objecting to exiting with an error message, but I think
letting ourselves be killed by a signal is no good.
Ok, I understand this point for this purpose.
--
Fabien.
--
Sent via pgsql-hackers
28.01.2016 18:12, Thom Brown:
On 28 January 2016 at 14:06, Anastasia Lubennikova
>
wrote:
31.08.2015 10:41, Anastasia Lubennikova:
Hi, hackers!
I'm going to begin work on effective storage of duplicate keys in
On Thu, Jan 28, 2016 at 9:09 AM, Filip Rembiałkowski
wrote:
> right.
Committed and back-patched to 9.5.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list
On Thu, Jan 28, 2016 at 6:37 AM, Magnus Hagander wrote:
> The PostgreSQL core team would like to welcome Dean Rasheed as a new
> committer for the PostgreSQL project.
Congratulations, Dean. Well deserved.
--
Peter Geoghegan
--
Sent via pgsql-hackers mailing list
On 01/28/2016 06:34 AM, Bruce Momjian wrote:
On Thu, Jan 28, 2016 at 09:31:46AM -0500, Robert Haas wrote:
On Thu, Jan 28, 2016 at 6:16 AM, Tomas Vondra
wrote:
How about
User-Interface-Bikeshedded-By:
?
+1
That's sort of implicitly pejorative. Maybe we could
On Fri, Jan 29, 2016 at 1:17 AM, Peter Eisentraut wrote:
> Some dump objects whose names are not unique on a schema level have
> insufficient details in the dump TOC. For example, a column default
> might have a TOC entry like this:
>
> 2153; 2604 39696 DEFAULT public a rolename
Hello Michaël,
v23 attached, which does not change the message but does the other fixes.
+if (coerceToInt() == INT64_MIN && coerceToInt() == -1)
+{
+ fprintf(stderr, "cannot divide INT64_MIN by -1\n");
+ return false;
+}
Bike-shedding:
On Fri, Jan 29, 2016 at 3:40 PM, Fabien COELHO wrote:
>
> I would as well suggest fixing first the (INT64_MAX / -1) crash on HEAD
>> and back-branches with something like the patch attached, inspired from
>> int8.c.
>>
>
> I think it is overkill, but do as you feel.
>
On Fri, Jan 29, 2016 at 3:51 PM, Tom Lane wrote:
>
> Michael Paquier writes:
> > On Fri, Jan 29, 2016 at 1:17 AM, Peter Eisentraut wrote:
> >> I think we should amend the archive tag for these kinds of objects to
> >> include the
Michael Paquier writes:
> On Fri, Jan 29, 2016 at 1:17 AM, Peter Eisentraut wrote:
>> I think we should amend the archive tag for these kinds of objects to
>> include the table name, so it might look like:
>>
>> 2153; 2604 39696 DEFAULT public test a
On 01/28/2016 04:00 PM, Stefan Kaltenbrunner wrote:
> Hi all!
>
> Per discussion in the afternoon break at FOSDEM/PGDay 2016 Developer
> Meeting we are going to upgrade gemulon.postgresql.org aka "gitmaster"
> today (the upgrade was originally scheduled end of last year but due to
> release and
On Wed, Jan 27, 2016 at 11:47 PM, Noah Misch wrote:
> On Wed, Jan 27, 2016 at 11:04:33PM -0500, Robert Haas wrote:
>> +Assert(portal->status != PORTAL_ACTIVE);
>> if (portal->status == PORTAL_ACTIVE)
>>
On Thu, Jan 28, 2016 at 11:04 AM, Stephen Frost wrote:
>> So, this seems like a case where a built-in role would be
>> well-justified. I don't really believe in built-in roles as a way of
>> bundling related permissions; I know you do, but I don't. I'd rather
>> see the
On 28 January 2016 at 17:09, Peter Geoghegan wrote:
> On Thu, Jan 28, 2016 at 9:03 AM, Thom Brown wrote:
>> I'm surprised that efficiencies can't be realised beyond this point. Your
>> results show a sweet spot at around 1000 / 1000, with it getting
>>
On 01/28/2016 03:37 PM, Robert Haas wrote:
On Thu, Jan 28, 2016 at 9:34 AM, Bruce Momjian wrote:
On Thu, Jan 28, 2016 at 09:31:46AM -0500, Robert Haas wrote:
On Thu, Jan 28, 2016 at 6:16 AM, Tomas Vondra
wrote:
How about
Michael Paquier wrote:
Well, 2015 is not making things easy visibly by not providing direct
ways to get locale information.
pgwin32_putenv broken too...
--
Yury Zhuravlev
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
--
Sent via pgsql-hackers mailing list
On Thu, Jan 28, 2016 at 11:26 AM, Ashutosh Bapat
wrote:
> 1. pg_fdw_core_v3.patch: changes in core - more description below
I've committed most of this patch, with some modifications. In
particular, I moved CachedPlanSource's hasForeignJoin flag to the
v22 compared to previous:
- remove the short macros (although IMO it is a code degradation)
- try not to remove/add blanks lines
- let some assert "as is"
- still exit on float to int overflow, see arguments in other mails
-
* Bruce Momjian (br...@momjian.us) wrote:
> On Thu, Jan 28, 2016 at 10:40:09AM -0500, Stephen Frost wrote:
> > * Joshua D. Drake (j...@commandprompt.com) wrote:
> > > On 01/28/2016 06:57 AM, Robert Haas wrote:
> > >
> > > >>I'm on board with Bruce's template as being a checklist of points to be
>
On 28 January 2016 at 17:03, Thom Brown wrote:
>
> On 28 January 2016 at 16:12, Anastasia Lubennikova <
> a.lubennik...@postgrespro.ru> wrote:
>
>>
>> 28.01.2016 18:12, Thom Brown:
>>
>> On 28 January 2016 at 14:06, Anastasia Lubennikova <
>> a.lubennik...@postgrespro.ru> wrote:
On Friday, 29 January 2016, Oleg Bartunov wrote:
> I read
> https://wiki.postgresql.org/wiki/FOSDEM/PGDay_2016_Developer_Meeting and
> would like to say thanks for such nice review of meeting.
>
+many
Thanks,
Amit
* Robert Haas (robertmh...@gmail.com) wrote:
> On Thu, Jan 28, 2016 at 11:04 AM, Stephen Frost wrote:
> >> So, this seems like a case where a built-in role would be
> >> well-justified. I don't really believe in built-in roles as a way of
> >> bundling related permissions; I
I read https://wiki.postgresql.org/wiki/FOSDEM/PGDay_2016_Developer_Meeting
and would like to say thanks for such nice review of meeting.
Oleg
> On Thu, Jan 28, 2016 at 10:50 AM, Kouhei Kaigai wrote:
> >> If I would make a proof-of-concept patch with interface itself, it
> >> seems to me file_fdw may be a good candidate for this enhancement.
> >> It is not a field for postgres_fdw.
> >>
> > The attached patch is
On 2016/01/28 23:53, Robert Haas wrote:
> On Thu, Jan 28, 2016 at 8:41 AM, Amit Langote wrote:
>> Or keep scanned_heap_pages as is and add a skipped_pages (or
>> skipped_heap_pages). I guess the latter would be updated not only for
>> all visible skipped pages but also
> total ForeignScandiff
> 0 workers: 17584.319 ms 17555.904 ms 28.415 ms
> 1 workers: 18464.476 ms 18110.968 ms 353.508 ms
> 2 workers: 19042.755 ms 14580.335 ms4462.420 ms
> 3 workers: 19318.254 ms 12668.912 ms6649.342 ms
> 4 workers:
On Fri, Jan 29, 2016 at 6:18 AM, Amit Langote wrote:
> On Friday, 29 January 2016, Oleg Bartunov wrote:
>> I read
>> https://wiki.postgresql.org/wiki/FOSDEM/PGDay_2016_Developer_Meeting and
>> would like to say thanks for such nice review of meeting.
On Fri, Jan 29, 2016 at 1:42 AM, Peter Geoghegan wrote:
> On Thu, Jan 28, 2016 at 6:37 AM, Magnus Hagander wrote:
>> The PostgreSQL core team would like to welcome Dean Rasheed as a new
>> committer for the PostgreSQL project.
>
> Congratulations, Dean. Well
Stephen Frost wrote:
> > OK, but keep in mind whatever script committers user should remove tags
> > that are empty after exiting the editor. I can provide the grep regex
> > in git somewhere too:
> >
> > egrep -v
> > "^(Author|Reported-by|Bug|Reviewed-by|Tested-by|Backpatch-through): *$"
>
On 01/28/2016 09:57 AM, Robert Haas wrote:
On Thu, Jan 28, 2016 at 9:52 AM, Tom Lane wrote:
Robert Haas writes:
On Thu, Jan 28, 2016 at 8:04 AM, Tomas Vondra
wrote:
Why can't we do both? That is, have a free-form
I do not think that it is really worth fixing, but I will not prevent anyone
to fix it.
I still think it does. Well, if there is consensus to address this one
and optionally the other integer overflows even on back branches, I'll
write a patch and let's call that a deal. This is not a problem
On 28 January 2016 at 16:36, Shulgin, Oleksandr <
oleksandr.shul...@zalando.de> wrote:
> On Thu, Jan 28, 2016 at 5:55 AM, Fujii Masao
> wrote:
>
>> On Wed, Jan 27, 2016 at 7:34 PM, Shulgin, Oleksandr
>> wrote:
>> > Hi,
>> >
>> > Please find
There has been a request in the FOSDEM developers meeting that
committers use a more consistent format for commit messages. This is
the format I use:
-- email subject limit -
-- gitweb summary limit --
>
> > Second issue:
> >
> > Mapping of levels between pg and journal levels is moved by1
>
> This is the same as how the "syslog" destination works.
>
>
I understand to this logic, but I miss any documentation.
Regards
Pavel
Hi Tomas,
Thanks for your comments and sorry for replying so late.
On 2016/01/22 22:54, Tomas Vondra wrote:
> thanks for working on this. Seems the last version of the patch was
> submitted more than 2 months ago and I believe large parts of it will get
> reworked based on the extensive
On Thu, Jan 28, 2016 at 5:55 AM, Fujii Masao wrote:
> On Wed, Jan 27, 2016 at 7:34 PM, Shulgin, Oleksandr
> wrote:
> > Hi,
> >
> > Please find attached a simple copy-paste fix for CREATE_REPLICATION_SLOT
> > syntax.
>
> We should change also
Etsuro Fujita wrote:
> On 2016/01/28 12:13, Robert Haas wrote:
> >I don't think this is a good idea. Most of the time, no system
> >columns will be present, and we'll just be scanning the Bitmapset
> >twice rather than once. Sure, that doesn't take many extra cycles,
> >but if the point of all
Hi
2016-01-28 3:50 GMT+01:00 Peter Eisentraut :
> On 1/27/16 7:02 AM, Pavel Stehule wrote:
> > The issues:
> >
> > 1. configure missing systemd integration test, compilation fails:
> >
> > postmaster.o postmaster.c
> > postmaster.c:91:31: fatal error: systemd/sd-daemon.h: No
On Thu, Jan 28, 2016 at 9:42 AM, Craig Ringer wrote:
>
>
> On 28 January 2016 at 16:36, Shulgin, Oleksandr <
oleksandr.shul...@zalando.de> wrote:
>>
>> On Thu, Jan 28, 2016 at 5:55 AM, Fujii Masao
wrote:
>>>
>>>
>>> We should change also
Hi,
I found that the following tab-completions for SET/RESET which
worked properly before doesn't work properly now in the master.
1. ALTER SYSTEM SET|RESET lists nothing.
2. ALTER DATABASE xxx SET lists nothing.
3. ALTER DATABASE xxx SET yyy lists nothing.
4. ALTER DATABASE xxx SET datestyle
On 2016/01/28 12:58, Robert Haas wrote:
On Thu, Jan 21, 2016 at 4:05 AM, Etsuro Fujita
wrote:
By the way, I'm not too sure I understand the need for the core
changes that are part of this patch, and I think that point merits
some discussion. Whenever you change
Hi all,
I found a couple of typos as per the $subject.
A patch is attached.
Regards,
--
Michael
diff --git a/contrib/pgcrypto/fortuna.c b/contrib/pgcrypto/fortuna.c
index 7ab888f..5028203 100644
--- a/contrib/pgcrypto/fortuna.c
+++ b/contrib/pgcrypto/fortuna.c
@@ -304,7 +304,7 @@
On 01/28/2016 01:57 PM, Robert Haas wrote:
...
One of the things I like about the current free-form approach is that
you can indicate nuances, like:
Person X reviewed an earlier version of this patch that was a lot
different than this one.
Person X reviewed this patch but didn't totally endorse
On Thu, Jan 28, 2016 at 8:51 PM, Yury Zhuravlev
wrote:
> Craig Ringer wrote:
>>
>> I strongly disagree. MSVC is a high quality compiler and the primary tool
>> for the platform.
>
> Ok. And we not suport MSVC2015 now. Either we support the platform normally
> or
On Thu, Jan 28, 2016 at 3:52 AM, Bruce Momjian wrote:
> There has been a request in the FOSDEM developers meeting that
> committers use a more consistent format for commit messages. This is
> the format I use:
>
> -- email subject limit
On 2016/01/28 18:15, Alvaro Herrera wrote:
Etsuro Fujita wrote:
On 2016/01/28 12:13, Robert Haas wrote:
I don't think this is a good idea. Most of the time, no system
columns will be present, and we'll just be scanning the Bitmapset
twice rather than once. Sure, that doesn't take many
On Thu, Jan 28, 2016 at 8:05 PM, Fujii Masao wrote:
> On Wed, Jan 20, 2016 at 2:35 PM, Masahiko Sawada
> wrote:
>> On Tue, Jan 19, 2016 at 1:52 AM, Thom Brown wrote:
>>> On 3 January 2016 at 13:26, Masahiko Sawada
On Thu, Jan 28, 2016 at 9:32 PM, Fujii Masao wrote:
> I found that the following tab-completions for SET/RESET which
> worked properly before doesn't work properly now in the master.
>
> 1. ALTER SYSTEM SET|RESET lists nothing.
> 2. ALTER DATABASE xxx SET lists nothing.
>
On Thu, Jan 28, 2016 at 11:30:58AM +0100, Tomas Vondra wrote:
> Any reason why not to adapt the git message conventions from kernel?
>
> https://git.wiki.kernel.org/index.php/CommitMessageConventions
>
> I'd expect there are tools already working with that format, making
> the life easier for
I'm closing this for the current commitfest as returned-with-feedback.
Please resubmit for the 2016-03 CF once you have it.
Thanks!
--
Álvaro Herrerahttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-hackers
Artur Zakirov wrote:
> I undo the changes and the error will be raised. I will update the patch
> soon.
I don't think you ever did this. I'm closing it now, but it sounds
useful stuff so please do resubmit for 2016-03.
--
Álvaro Herrerahttp://www.2ndQuadrant.com/
PostgreSQL
Michael Paquier wrote:
Many companies use it, including mine, and likely EDB.
Ok, why? I wonder why it is?
--
Yury Zhuravlev
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to
So even if the main packages switched to
compiling with mingw, we'd probably still want to support MSVC.
MinGV more accessible. We can always say that after the release of X is not
supported by the MSVC.
I do not propose to abandon the MSVC but its use to be justified.
Are we moving forward
On 28.01.2016 14:19, Alvaro Herrera wrote:
Artur Zakirov wrote:
I undo the changes and the error will be raised. I will update the patch
soon.
I don't think you ever did this. I'm closing it now, but it sounds
useful stuff so please do resubmit for 2016-03.
I'm working on the patch. I
On Wed, Jan 20, 2016 at 2:35 PM, Masahiko Sawada wrote:
> On Tue, Jan 19, 2016 at 1:52 AM, Thom Brown wrote:
>> On 3 January 2016 at 13:26, Masahiko Sawada wrote:
>>> On Fri, Dec 25, 2015 at 7:21 AM, Thomas Munro
>>>
Dne 28. 1. 2016 11:57 napsal uživatel "Alvaro Herrera" <
alvhe...@2ndquadrant.com>:
>
> Magnus Hagander wrote:
>
> > They also had tested-by, it might be an idea to include that as well?
>
> How about
> User-Interface-Bikeshedded-By:
> ?
+1
>
> --
> Álvaro Herrera
Craig Ringer wrote:
Yeah, strongly agree there.
CMake has excellent MSVC support btw.
Yes... but I found only hack way for call gendef.pl in pre_link stage (get
objects folder name). CMake suggests that we use for normal MSVC ways to
create dll.
OTOH MinGW relies on reverse-engineered
On Thu, Jan 28, 2016 at 03:52:00AM -0500, Bruce Momjian wrote:
> There has been a request in the FOSDEM developers meeting that
> committers use a more consistent format for commit messages. This is
> the format I use:
Here is an updated version that includes a potential bug number:
--
Hi,
On 01/28/2016 11:06 AM, Bruce Momjian wrote:
On Thu, Jan 28, 2016 at 03:52:00AM -0500, Bruce Momjian wrote:
There has been a request in the FOSDEM developers meeting that
committers use a more consistent format for commit messages. This is
the format I use:
Here is an updated version
>+if(!scan_all)
>+scanned_heap_pages = scanned_heap_pages +
>next_not_all_visible_block;
>I don't want to be too much of a stickler for details here, but it
>seems to me that this is an outright lie.
Initially the scanned_heap_pages were meant to report just
Magnus Hagander wrote:
> They also had tested-by, it might be an idea to include that as well?
How about
User-Interface-Bikeshedded-By:
?
--
Álvaro Herrerahttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via
Bruce Momjian wrote:
> There has been a request in the FOSDEM developers meeting that
> committers use a more consistent format for commit messages.
Let me point out that the reason this is being put forward is to make
sure we have the reviewers listed for each patch, so that we can add a
Joe Conway wrote:
> Ok, back to the drawing board. Thanks for the feedback.
Closing this one as returned-with-feedback. Please do resubmit for
CF 2016-03.
--
Álvaro Herrerahttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
I think this is very exciting stuff, but since you didn't submit an
updated patch after David's review, I'm closing it for now as
returned-with-feedback. Please submit a new version once you have it.
--
Álvaro Herrerahttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7
On Thu, Jan 28, 2016 at 11:49 AM, Bruce Momjian wrote:
> On Thu, Jan 28, 2016 at 11:30:58AM +0100, Tomas Vondra wrote:
> > Any reason why not to adapt the git message conventions from kernel?
> >
> > https://git.wiki.kernel.org/index.php/CommitMessageConventions
> >
> > I'd
On Thu, Jan 28, 2016 at 4:53 PM, Dilip Kumar wrote:
> I did not find in regression in normal case.
> Note: I tested it with previous patch extend_num_pages=10 (guc parameter)
> so that we can see any impact on overall system.
>
Just forgot to mentioned That i have run
On Thu, Jan 28, 2016 at 11:53:44AM +0100, Magnus Hagander wrote:
> The original format uses the author for that (author != committer in git), but
> that changes how we work a bit more. I'd be happy to just clal it "Author"
> rather than "Patch-by".
>
> I also suggest a - in "Backpatch-through:"
On Mon, Jan 25, 2016 at 11:59 AM, Dilip Kumar wrote:
1.
>> Patch is not getting compiled.
>>
>> 1>src/backend/access/heap/hio.c(480): error C2065: 'buf' : undeclared
>> identifier
>>
> Oh, My mistake, my preprocessor is ignoring this error and relacing it
> with BLKSIZE
>
Craig Ringer wrote:
I strongly disagree. MSVC is a high quality compiler and the
primary tool for the platform.
Ok. And we not suport MSVC2015 now. Either we support the platform normally
or throwing it.
Now it all looks like a zombie.
--
Yury Zhuravlev
Postgres Professional:
Sorry, I don't know why this thread was moved to another thread.
I duplicate the patch here.
On 28.01.2016 14:19, Alvaro Herrera wrote:
Artur Zakirov wrote:
I undo the changes and the error will be raised. I will update the patch
soon.
I don't think you ever did this. I'm closing it now,
On Thu, Jan 28, 2016 at 10:50 PM, Masahiko Sawada wrote:
> On Thu, Jan 28, 2016 at 10:15 PM, Michael Paquier
> wrote:
>> On Thu, Jan 28, 2016 at 9:32 PM, Fujii Masao wrote:
>>> I found that the following tab-completions
On Thu, Jan 28, 2016 at 10:15 PM, Michael Paquier
wrote:
> On Thu, Jan 28, 2016 at 9:32 PM, Fujii Masao wrote:
>> I found that the following tab-completions for SET/RESET which
>> worked properly before doesn't work properly now in the master.
>>
> On Mon, Jan 25, 2016 at 8:06 PM, Kouhei Kaigai wrote:
> > Sorry for my late response. I've been unavailable to have enough
> > time to touch code for the last 1.5 month.
> >
> > The attached patch is a revised one to handle private data of
> > foregn/custom scan node more
On Fri, Jan 29, 2016 at 11:53 AM, Fujii Masao wrote:
> I removed the above and added the following for that case.
>
> +/* Complete ALTER DATABASE|FUNCTION|ROLE|USER ... SET */
> +else if (Matches2("ALTER", "DATABASE|FUNCTION|ROLE|USER") &&
> +
On Thu, Jan 28, 2016 at 11:26 AM, Ashutosh Bapat
wrote:
> 2. pg_fdw_join_v3.patch: changes to postgres_fdw - more description below
This patch no longer quite applies because of conflicts with one of
your other patches that I applied today (cf. commit
On Thu, Jan 28, 2016 at 10:18 PM, Kouhei Kaigai wrote:
> Do you think we shall allow to register same extensible node name for
> different node types? Like, "GpuJoin" for any of CustomPath, CustomScan
> and CustomScanState. Or, do we avoid this using different name for each?
> On Thu, Jan 28, 2016 at 10:18 PM, Kouhei Kaigai wrote:
> > Do you think we shall allow to register same extensible node name for
> > different node types? Like, "GpuJoin" for any of CustomPath, CustomScan
> > and CustomScanState. Or, do we avoid this using different name
On Thu, Jan 28, 2016 at 09:31:46AM -0500, Robert Haas wrote:
> On Thu, Jan 28, 2016 at 6:16 AM, Tomas Vondra
> wrote:
> >> How about
> >> User-Interface-Bikeshedded-By:
> >> ?
> >
> > +1
>
> That's sort of implicitly pejorative. Maybe we could find another
> way
Hello!
The PostgreSQL core team would like to welcome Dean Rasheed as a new
committer for the PostgreSQL project.
Dean - welcome! Now let's see how quickly you can break the buildfarm!
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
On Thu, Jan 28, 2016 at 9:34 AM, Bruce Momjian wrote:
> On Thu, Jan 28, 2016 at 09:31:46AM -0500, Robert Haas wrote:
>> On Thu, Jan 28, 2016 at 6:16 AM, Tomas Vondra
>> wrote:
>> >> How about
>> >> User-Interface-Bikeshedded-By:
>> >> ?
>> >
>> >
On 27.01.2016 15:28, Artur Zakirov wrote:
On 27.01.2016 14:14, Stas Kelvich wrote:
Hi.
I tried that and confirm strange behaviour. It seems that problem with
small cyrillic letter ‘х’. (simplest obscene language filter? =)
That can be reproduced with simpler test
Stas
The test program
On 01/28/2016 06:37 AM, Magnus Hagander wrote:
Hello!
The PostgreSQL core team would like to welcome Dean Rasheed as a new
committer for the PostgreSQL project.
Dean - welcome! Now let's see how quickly you can break the buildfarm!
Congrats!
--
Magnus Hagander
Me:
Hi Peter,
thanks for working on this, I'm looking forward to make Debian's
pg_*cluster tools work with that (and hopefully be able to remove tons
of legacy code).
If a cluster is configured for non-hot-standby replication, the
READY=1 seems to never happen. Did you check if that doesn't trigger
On Thu, Jan 28, 2016 at 9:43 AM, Joshua D. Drake wrote:
> On 01/28/2016 06:37 AM, Magnus Hagander wrote:
>> The PostgreSQL core team would like to welcome Dean Rasheed as a new
>> committer for the PostgreSQL project.
>>
>> Dean - welcome! Now let's see how quickly you can
Robert>Hmm, so in your example, you actually want replanning to be able to
Robert>change the cached plan's result type?
I want backend to cache _several_ plans behind a single "statement name".
I want to treat "prepare...exec...deallocate" dance as an optimization
step for a simple
Robert Haas wrote:
> On Thu, Jan 28, 2016 at 6:16 AM, Tomas Vondra
> wrote:
> >> How about
> >> User-Interface-Bikeshedded-By:
> >> ?
> >
> > +1
>
> That's sort of implicitly pejorative. Maybe we could find another
> way to phrase that, like
On Thu, Jan 28, 2016 at 5:37 PM, Magnus Hagander
wrote:
> Hello!
>
> The PostgreSQL core team would like to welcome Dean Rasheed as a new
> committer for the PostgreSQL project.
>
> Dean - welcome! Now let's see how quickly you can break the buildfarm!
>
Congratulations, of
Robert Haas writes:
> On Thu, Jan 28, 2016 at 8:04 AM, Tomas Vondra
> wrote:
>> Why can't we do both? That is, have a free-form text with the nuances, and
>> then Reviewed-By listing the main reviewers? The first one is for humans,
>> the
Hi,
On Thu, Jan 28, 2016 at 7:38 PM, Rahila Syed wrote:
>>+if(!scan_all)
>>+scanned_heap_pages = scanned_heap_pages +
>>next_not_all_visible_block;
>
>>I don't want to be too much of a stickler for details here, but it
>>seems to me
On Thu, Jan 28, 2016 at 10:15 PM, Michael Paquier
wrote:
> On Thu, Jan 28, 2016 at 9:32 PM, Fujii Masao wrote:
>> I found that the following tab-completions for SET/RESET which
>> worked properly before doesn't work properly now in the master.
>>
1 - 100 of 122 matches
Mail list logo