At Thu, 9 Sep 2021 16:06:25 +0900, Abhishek Bhola
wrote in
> sourcedb:~$ postgres --version
> postgres (PostgreSQL) 11.6
>
> Sorry for missing this information.
> But looks like this fix is already included in the version I am running.
Ok. I'm not sure but there may be a case where too-busy (o
On 2021-09-06 07:13:07 -0700, David G. Johnston wrote:
> On Monday, September 6, 2021, Philippe Doussot
> wrote:
>
> I whas hopping the same optimisation as you: Write in place.
>
> How exactly would you expect “update-in-place” to work given the nature of
> MVCC?
Some databases (e.g. Oracl
Richard Michael writes:
> Would a tiny patch to the PREPARE docs be accepted? I'd like to help
> clarify investigating `plan_cache_mode` for future readers.
What did you have in mind?
(I'm kind of allergic to documenting the plan-caching behavior in too
much detail, because I keep expecting us
Hi Tom,
On Thu, Sep 9, 2021 at 6:02 PM Tom Lane wrote:
> Richard Michael writes:
> > After reading Laurenz's reply, I experimented again with `PREPARE
> > basic(int) AS SELECT $1 AS number;" and the query plan logged in the log
> > file (by auto_explain) does indeed show "Output: $1" on the six
Richard Michael writes:
> After reading Laurenz's reply, I experimented again with `PREPARE
> basic(int) AS SELECT $1 AS number;" and the query plan logged in the log
> file (by auto_explain) does indeed show "Output: $1" on the sixth EXPLAIN
> EXECUTE! Sorry I missed this earlier. (The EXPLAIN
Hi David,
On Sun, Sep 5, 2021 at 8:32 PM David G. Johnston
wrote:
> On Sunday, September 5, 2021, Richard Michael
> wrote:
>
>>
>> Based on the documentation, I expected the first planned query text to
>> be: `SELECT 10 AS data`, since it should be a custom plan with
>> substituted values. How
Hi Laurenz,
Thank you for the quick response and clear demonstration. I have a few
comments, inline below.
On Mon, Sep 6, 2021 at 8:26 AM Laurenz Albe
wrote:
> On Sun, 2021-09-05 at 14:20 -0400, Mladen Gogala wrote:
> > On 9/5/21 9:35 AM, Richard Michael wrote:
> > > TL;DR --
> > >
> > > 1/ My
Ok thanks.
On Thu, Sep 9, 2021 at 9:06 PM Ian Lawrence Barwick wrote:
>
> 2021年9月9日(木) 16:53 Tim Uckun :
> >
> > This seems simple enough but it's not working.
> >
> > alter database dbname set "blah.blah" = 'test_value' ;
> >
> > The above statement returns with no errors.
> >
> > select curren
On Thu, 9 Sept 2021 at 06:54, Avi Weinberg wrote:
> I have a publisher with around 30 tables. I have two types of subscribers.
> Both types needs 25 "common" tables from the publisher plus 2-3 specific
> tables for each type of subscriber.
>
> For maintenance and monitoring reasons it is bett
2021年9月9日(木) 16:53 Tim Uckun :
>
> This seems simple enough but it's not working.
>
> alter database dbname set "blah.blah" = 'test_value' ;
>
> The above statement returns with no errors.
>
> select current_setting('blah.blah')
>
> The above statement returns a record with null
Open a new databa
This seems simple enough but it's not working.
alter database dbname set "blah.blah" = 'test_value' ;
The above statement returns with no errors.
select current_setting('blah.blah')
The above statement returns a record with null
Also how long does the "ALTER DATABASE SET" last? Will it surviv
sourcedb:~$ postgres --version
postgres (PostgreSQL) 11.6
Sorry for missing this information.
But looks like this fix is already included in the version I am running.
Regards,
Abhishek Bhola
On Thu, Sep 9, 2021 at 3:56 PM Kyotaro Horiguchi
wrote:
> At Thu, 9 Sep 2021 14:52:25 +0900, Abhishek B
12 matches
Mail list logo
