> On 30 Mar 2024, at 11:39, Karl O. Pinc wrote:
>
> Well, Friday has come and gone and I've not gotten to this.
> I'll see if I can spend time tomorrow.
No worries, Karl! I just wanted to know if anyone is interested in this thread,
and, now is obvious that you are. Thanks for your work!
B
On Thu, 28 Mar 2024 08:28:16 -0400
Robert Treat wrote:
> I spoke with Karl briefly on this and he is working on getting an
> updated patch together. The work now involves incorporating feedback
> and some rebasing, but hopefully we will see something in the next few
> days.
Well, Friday has come
On Thu, Mar 28, 2024 at 8:16 AM Andrey M. Borodin wrote:
> > On 1 Dec 2023, at 19:00, Karl O. Pinc wrote:
> >
> > I won't be able to submit
> > new patches based on reviews for 2 weeks.
>
> Hi everyone!
>
> Is there any work going on? Maybe is someone interested in moving this
> forward?
>
> Th
> On 1 Dec 2023, at 19:00, Karl O. Pinc wrote:
>
> I won't be able to submit
> new patches based on reviews for 2 weeks.
Hi everyone!
Is there any work going on? Maybe is someone interested in moving this forward?
Thanks!
Best regards, Andrey Borodin.
Hello,
Thank you all for your help. I won't be able to submit
new patches based on reviews for 2 weeks.
On Thu, 30 Nov 2023 16:02:28 +0530
Shubham Khanna wrote:
> -v7-0012-Explain-role-management.patch
>
> + The managment of most database objects is by way of granting some
> role
>
> Here
On Thu, Nov 30, 2023 at 3:59 PM David G. Johnston
wrote:
>
> Extending my prior email which is now redundant.
>
> On Tue, Oct 3, 2023 at 7:00 PM David G. Johnston
> wrote:
>>
>> On Tue, Oct 3, 2023 at 4:15 PM Karl O. Pinc wrote:
>>>
>>> On Tue, 3 Oct 2023 14:51:31 -0700
>>> "David G. Johnston"
Extending my prior email which is now redundant.
On Tue, Oct 3, 2023 at 7:00 PM David G. Johnston
wrote:
> On Tue, Oct 3, 2023 at 4:15 PM Karl O. Pinc wrote:
>
>> On Tue, 3 Oct 2023 14:51:31 -0700
>> "David G. Johnston" wrote:
>>
>> Isn't the entire section about "deviating from the normal flo
On Tue, Oct 3, 2023 at 4:15 PM Karl O. Pinc wrote:
> On Tue, 3 Oct 2023 14:51:31 -0700
> "David G. Johnston" wrote:
>
> Isn't the entire section about "deviating from the normal flow of the
> code"? That's what makes me want "Exception" in the section title.
>
It is about how error handling in
On Tue, 3 Oct 2023 14:51:31 -0700
"David G. Johnston" wrote:
> 0001 - I would just call the section:
> Capturing Command Results into Variables
I like your wording a lot. Let's use it!
> I would add commentary in there that it is only possible for
> variables to take on single value at any giv
On Tue, Oct 3, 2023 at 10:56 AM Karl O. Pinc wrote:
> On Mon, 2 Oct 2023 15:18:32 -0500
> "Karl O. Pinc" wrote:
>
> Version 7
>
>
0001 - I would just call the section:
Capturing Command Results into Variables
I would add commentary in there that it is only possible for variables to
take on singl
On Mon, 2 Oct 2023 15:18:32 -0500
"Karl O. Pinc" wrote:
Version 7
Added:
v7-0016-Predicate-locks-are-held-per-cluster-not-per-data.patch
> > > On Mon, 25 Sep 2023 23:37:44 -0500
> > > "Karl O. Pinc" wrote:
> > >
> > > > > On Mon, 25 Sep 2023 17:55:59 -0500
> > > > > "Karl O. Pinc" wrote:
On Sun, 1 Oct 2023 18:18:07 -0500
"Karl O. Pinc" wrote:
Version 6
Added:
v6-0015-Trigger-authors-need-not-worry-about-parallelism.patch
Can't say if this is an awesome idea or not. (Might have saved me time.)
Read the commit message for a justification.
> > On Mon, 25 Sep 2023 23:37:44 -050
Version 5, this time with attachments.
Changed word order in a sentence:
v5-0012-Explain-role-management.patch
Added a hyperlink:
v5-0013-Hyperlink-from-CREATE-FUNCTION-reference-page-to-.patch
Added 3 index entries:
v5-0014-Add-index-entries-for-parallel-safety.patch
> On Mon, 25 Sep 2023 23:3
Version 5
Changed word order in a sentence:
v5-0012-Explain-role-management.patch
Added a hyperlink:
v5-0013-Hyperlink-from-CREATE-FUNCTION-reference-page-to-.patch
Added 3 index entries:
v5-0014-Add-index-entries-for-parallel-safety.patch
> On Mon, 25 Sep 2023 23:37:44 -0500
> "Karl O. Pinc"
Version 4.
Added: v4-0012-Explain-role-management.patch
On Mon, 25 Sep 2023 23:37:44 -0500
"Karl O. Pinc" wrote:
> > On Mon, 25 Sep 2023 17:55:59 -0500
> > "Karl O. Pinc" wrote:
> >
> > > On Mon, 25 Sep 2023 14:14:37 +0200
> > > Daniel Gustafsson wrote:
> >
> > > > Once done you can
Forgot to attach. Sorry.
On Mon, 25 Sep 2023 23:30:38 -0500
"Karl O. Pinc" wrote:
> Version 3.
>
> Re-do title, which is all of patch v3-003.
>
> On Mon, 25 Sep 2023 17:55:59 -0500
> "Karl O. Pinc" wrote:
>
> > On Mon, 25 Sep 2023 14:14:37 +0200
> > Daniel Gustafsson wrote:
>
> > > Once
Version 3.
Re-do title, which is all of patch v3-003.
On Mon, 25 Sep 2023 17:55:59 -0500
"Karl O. Pinc" wrote:
> On Mon, 25 Sep 2023 14:14:37 +0200
> Daniel Gustafsson wrote:
> > Once done you can do "git format-patch origin/master -v 1" which
> > will generate a set of n patches named v1-000
On Mon, 25 Sep 2023 14:14:37 +0200
Daniel Gustafsson wrote:
> > On 25 Sep 2023, at 14:00, Karl O. Pinc wrote:
>
> > Is there a preferred data format or should I send
> > each patch in a separate attachment with description?
> Once done you can do "git format-patch origin/master -v 1" which
> On 25 Sep 2023, at 14:00, Karl O. Pinc wrote:
> Is there a preferred data format or should I send
> each patch in a separate attachment with description?
The easiest way would be to create a patchset off of master I think. In a
branch, commit each change with an explanatory commit message. O
On Mon, 25 Sep 2023 09:26:38 +0200
Daniel Gustafsson wrote:
> > On 25 Sep 2023, at 00:57, Karl O. Pinc wrote:
>
> > I have made various, mostly unrelated to each other,
> > small improvements to the documentation.
> While I agree it's subjective, I don't think adding a new section or
> par
> On 25 Sep 2023, at 00:57, Karl O. Pinc wrote:
> I have made various, mostly unrelated to each other,
> small improvements to the documentation. These
> are usually in the areas of plpgsql, schemas, and permissions.
> Most change 1 lines, but some supply short overviews.
>
> "Short" is subject
Hi,
I have made various, mostly unrelated to each other,
small improvements to the documentation. These
are usually in the areas of plpgsql, schemas, and permissions.
Most change 1 lines, but some supply short overviews.
"Short" is subjective, so if these need to be
broken into different threads
22 matches
Mail list logo
