Now you can say that'd be solved by bumping the cost up, sure. But
obviously the row / cost model is pretty much out of whack here, I don't
see how we can make reasonable decisions in a trivial query that has a
misestimation by five orders of magnitude.
Before JIT, it didn't matter whether the
WalSndLoop() does this, simplifying considerably:
for (;;)
{
/* does: last_reply_timestamp = GetCurrentTimestamp() */
ProcessRepliesIfAny();
send_data(); /* e.g. XLogSendPhysical(), which calls
XLogRead() */
WalSnd
Robert Haas writes:
> I'm not sure that it's a good idea to change this behavior.
> In the case of an unqualified name, the permissions on the schemas in
> the search path can affect which table is chosen in the first place.
> ... So I think this only matters for qualified names.
Yeah, that agre
On Mon, Aug 20, 2018 at 4:57 PM Michael Paquier wrote:
>
> On Mon, Aug 20, 2018 at 04:38:20PM +1200, Thomas Munro wrote:
> > "For examples of usage look at simplehash.c ..."
> >
> > There is no such file in the tree. Maybe this should say tidbitmap.c?
>
> And execGrouping.c...
Some more comments
Robert-san,
Thank you very much for your comment.
I will try to modify it so that GUC can be added more generically.
When specifying multiple GUC settings for PQconnectdbParams, is it correct to
describe as follows?
--
keywords [n] = "options";
values [n] = "-c work_mem=8MB -c maintenance_work_m
On Fri, Aug 24, 2018 at 5:31 AM, Yugo Nagata wrote:
> Although the behavior of the original function would reflect pg_class.relacl,
> it seems to
> me that the function fixed in my patch is more useful for users because this
> reflects
> the actual accessibility during query execution.
I'm not
On Wed, Aug 22, 2018 at 6:43 PM, Andres Freund wrote:
> Now you can say that'd be solved by bumping the cost up, sure. But
> obviously the row / cost model is pretty much out of whack here, I don't
> see how we can make reasonable decisions in a trivial query that has a
> misestimation by five ord
On Tue, Aug 21, 2018 at 9:10 AM, Alexander Korotkov
wrote:
> After heap truncation using this algorithm, shared buffers may contain
> past-OEF buffers. But those buffers are empty (no used items) and
> clean. So, real-only queries shouldn't hint those buffers dirty
> because there are no used it
On Sat, Aug 25, 2018 at 2:18 PM, Bruce Momjian wrote:
>> I think that's less "our" logic and more yours, that has become
>> established because you've done most of the major release notes for a
>> long time. I'm not trying to say that that's wrong or anything, just
>
> I don't do my work in a vacu
On Sat, Aug 25, 2018 at 12:17:17PM -0700, Andres Freund wrote:
> Hi,
>
> On 2018-08-25 14:47:20 -0400, Bruce Momjian wrote:
> > Well, our normal logical is whether the average user would adjust their
> > behavior based on this change, or whether it is user visible. I thought
> > it was a contrive
Hi,
On 2018-08-25 14:47:20 -0400, Bruce Momjian wrote:
> Well, our normal logical is whether the average user would adjust their
> behavior based on this change, or whether it is user visible. I thought
> it was a contrived-enough query that this was not the case, but I would
> be interested to h
On Sat, Aug 25, 2018 at 11:42:35AM -0700, Andres Freund wrote:
>
>
> On August 25, 2018 11:41:11 AM PDT, Bruce Momjian wrote:
> >On Sun, Aug 12, 2018 at 11:21:26AM +0200, Adrien Nayrat wrote:
> >> Hello,
> >>
> >> It seems this feature is missing in releases notes ?
> >>
> >> commit 1f6d515a67
On August 25, 2018 11:41:11 AM PDT, Bruce Momjian wrote:
>On Sun, Aug 12, 2018 at 11:21:26AM +0200, Adrien Nayrat wrote:
>> Hello,
>>
>> It seems this feature is missing in releases notes ?
>>
>> commit 1f6d515a67ec98194c23a5db25660856c9aab944
>> Author: Robert Haas
>> Date: Mon Aug 21 14:
On Sun, Aug 12, 2018 at 11:21:26AM +0200, Adrien Nayrat wrote:
> Hello,
>
> It seems this feature is missing in releases notes ?
>
> commit 1f6d515a67ec98194c23a5db25660856c9aab944
> Author: Robert Haas
> Date: Mon Aug 21 14:43:01 2017 -0400
>
> Push limit through subqueries to underlying
On Wed, Aug 22, 2018 at 06:20:21AM +, Noah Misch wrote:
> On Wed, Mar 28, 2018 at 02:27:51PM -0700, Andres Freund wrote:
> > For now LLVM is enabled by default when compiled --with-llvm. I'm mildly
> > inclined to leave it like that until shortly before the release, and
> > then disable it by d
On Fri, Aug 17, 2018 at 09:57:08AM +0200, Paul Bonaud wrote:
> I shared the pach in plain textin the email body and figured out that
> all other patches are submitted as an attachement. Sorry for that, here
> is the patch attached to this email.
Patch applied through 9.5, where the "match" text fi
Andres Freund writes:
> On 2018-08-16 11:41:30 -0400, Tom Lane wrote:
>> Andres Freund writes:
>>> While I'd personally have no problem kicking gcc 3.4 to the curb, I'm
>>> still confused what causes this error mode. Kinda looks like
>>> out-of-sync headers with gcc or something.
>> Yeah, this
On Fri, Aug 24, 2018 at 05:38:44PM +0530, Ashutosh Sharma wrote:
> Hi All,
>
> The redirect link for applicable_roles view is missing in the
> documentation page for enabled_roles view. Attached is the patch that
> adds the same. Please refer to the following URL for details.
>
> https://www.post
On Wed, Aug 1, 2018 at 12:56 PM Kyotaro HORIGUCHI
wrote:
>
> Thank you, Amit, Michael.
>
Can you verify the first patch that I have posted above [1]? We can
commit it separately.
>
> It's a long time ago.. Let me have a bit of time to blow dust off..
>
> https://www.postgresql.org/message-id/20
19 matches
Mail list logo
