On Tue, May 14, 2024 at 09:52:35AM -0400, Robert Haas wrote:
> We are down to three open items, all of which have proposed fixes.
> That is great, but we need to keep things moving along, because
> according to https://wiki.postgresql.org/wiki/PostgreSQL_17_Open_Items
> we are due to r
Hi,
We are down to three open items, all of which have proposed fixes.
That is great, but we need to keep things moving along, because
according to https://wiki.postgresql.org/wiki/PostgreSQL_17_Open_Items
we are due to release beta1 on May 23. That means that a release
freeze will be in effect
On 09/05/2024 22:39, Robert Haas wrote:
On Thu, May 9, 2024 at 3:38 PM Dagfinn Ilmari Mannsåker
wrote:
Robert Haas writes:
* Register ALPN protocol id with IANA. From the mailing list thread,
it is abundantly clear that IANA is in no hurry to finish dealing with
what seems to be a completely
On Fri, May 10, 2024 at 7:14 AM Alvaro Herrera wrote:
> A possible complaint is that the upgrade mechanics which are mostly in
> pg_dump with some pieces in pg_upgrade are not very explicitly
> documented. There are already comments in all relevant places, but
> perhaps an overall picture is nece
On Fri, May 10, 2024 at 8:48 AM Melanie Plageman
wrote:
> Sorry, yes, the trivial fix has been done for a while. There is one
> outstanding feedback on the patch: an update to one of the comments
> suggested by Tomas. I got distracted by trying to repro and fix a bug
> from the section "live issue
> On 10 May 2024, at 14:48, Melanie Plageman wrote:
>
> On Thu, May 9, 2024 at 3:28 PM Robert Haas wrote:
>>
>> Just a few reminders about the open items list at
>> https://wiki.postgresql.org/wiki/PostgreSQL_17_Open_Items --
>>
>> * Incorrect Assert
On Thu, May 9, 2024 at 3:28 PM Robert Haas wrote:
>
> Just a few reminders about the open items list at
> https://wiki.postgresql.org/wiki/PostgreSQL_17_Open_Items --
>
> * Incorrect Assert in heap_end/rescan for BHS. Either the description
> of this item is inaccurate, or we
On 2024-May-09, Robert Haas wrote:
> * not null constraints break dump/restore. I asked whether all of the
> issues had been addressed here and Justin Pryzby opined that the only
> thing that was still relevant for this release was a possible test
> case change, which I would personally consider a
On Thu, May 09, 2024 at 03:28:13PM -0400, Robert Haas wrote:
> Just a few reminders about the open items list at
> https://wiki.postgresql.org/wiki/PostgreSQL_17_Open_Items --
Thanks for summarizing the situation.
> * Race condition with local injection point detach. Discussion is on
On Thu, May 9, 2024 at 3:38 PM Dagfinn Ilmari Mannsåker
wrote:
> Robert Haas writes:
> > * Register ALPN protocol id with IANA. From the mailing list thread,
> > it is abundantly clear that IANA is in no hurry to finish dealing with
> > what seems to be a completely pro forma request from our end
Robert Haas writes:
> * Register ALPN protocol id with IANA. From the mailing list thread,
> it is abundantly clear that IANA is in no hurry to finish dealing with
> what seems to be a completely pro forma request from our end. I think
> we just have to be patient.
This appears to have been appr
Hi,
Just a few reminders about the open items list at
https://wiki.postgresql.org/wiki/PostgreSQL_17_Open_Items --
- Please don't add issues to this list unless they are the result of
development done during this release cycle. This is not a
general-purpose bug tracker.
- The owner of an
On Sat, Mar 9, 2019 at 1:03 AM Michael Paquier wrote:
>
> On Fri, Mar 08, 2019 at 10:06:43PM +0900, Amit Langote wrote:
> > On Fri, Mar 8, 2019 at 7:52 PM Julien Rouhaud wrote:
> >> It seems like a good timing to me.
>
> It would be a good timing as some issues are already showing up. And
> abra
On Sat, 9 Mar 2019 at 13:03, Michael Paquier wrote:
> It would be a good timing as some issues are already showing up. And
> abracadabra:
> https://wiki.postgresql.org/wiki/PostgreSQL_12_Open_Items
Thanks.
--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development,
On Fri, Mar 08, 2019 at 10:06:43PM +0900, Amit Langote wrote:
> On Fri, Mar 8, 2019 at 7:52 PM Julien Rouhaud wrote:
>> It seems like a good timing to me.
It would be a good timing as some issues are already showing up. And
abracadabra:
https://wiki.postgresql.org/wiki/PostgreSQL_12_Open_Items
-
On Fri, Mar 8, 2019 at 7:52 PM Julien Rouhaud wrote:
>
> On Fri, Mar 8, 2019 at 11:49 AM David Rowley
> wrote:
> >
> > Is it too soon for a PG12 open items wiki page?
>
> It seems like a good timing to me.
>
> > I've got a few things I need to keep tr
On Fri, Mar 8, 2019 at 11:49 AM David Rowley
wrote:
>
> Is it too soon for a PG12 open items wiki page?
It seems like a good timing to me.
> I've got a few things I need to keep track of. Normally writing a
> patch and putting on the next open CF is a good move, but since the
Is it too soon for a PG12 open items wiki page?
I've got a few things I need to keep track of. Normally writing a
patch and putting on the next open CF is a good move, but since the
next one is not for PG12, it seems like not the best place.
Any objections to me making one now?
--
> On Apr 12, 2018, at 9:24 AM, Ashutosh Bapat
> wrote:
>
> On Thu, Apr 12, 2018 at 6:52 PM, Alvaro Herrera
> wrote:
>>
>> Now, maybe what you suggest for open items is to create a separate view
>> using much of the commitfest app code, say
>> https://
On Thu, Apr 12, 2018 at 6:52 PM, Alvaro Herrera wrote:
>
> Now, maybe what you suggest for open items is to create a separate view
> using much of the commitfest app code, say
> https://commitfest.postgresql.org/openitems/NNN
> I think that would probably work well.
Yes, that&
Ashutosh Bapat wrote:
> On Thu, Apr 12, 2018 at 6:27 PM, Alvaro Herrera
> wrote:
> > Ashutosh Bapat wrote:
> >
> >> We use commitfest app for tracking the patches submitted. It has done
> >> well. Can we re-purpose the same for tracking open items?
> >
On Thu, Apr 12, 2018 at 6:27 PM, Alvaro Herrera wrote:
> Ashutosh Bapat wrote:
>
>> We use commitfest app for tracking the patches submitted. It has done
>> well. Can we re-purpose the same for tracking open items?
>
> I think the rules are too different to cram both in
Ashutosh Bapat wrote:
> We use commitfest app for tracking the patches submitted. It has done
> well. Can we re-purpose the same for tracking open items?
I think the rules are too different to cram both in the same place.
--
Álvaro Herrerahttps://www.2ndQuadrant.com/
Post
On Thu, Apr 12, 2018 at 11:46:33AM +0530, Ashutosh Bapat wrote:
> Usually there are threads associated with the open items, then there
> are patches to solve those and owners responsible in resolving them.
> We have all the infrastructure in the commitfest app to track those
> thing
On Wed, Apr 11, 2018 at 10:33 PM, Magnus Hagander wrote:
> On Wed, Apr 11, 2018 at 6:57 PM, Andres Freund wrote:
>>
>> On 2018-04-11 13:54:34 -0300, Alvaro Herrera wrote:
>> > The other proposal was that we could have a simple web app to track open
>> > items
On Thu, Apr 12, 2018 at 2:31 AM, Tom Lane wrote:
> Peter Eisentraut writes:
>> On 4/11/18 10:53, Tom Lane wrote:
>>> It's not that much work to move the items rather than remove them,
>
>> Well, toward the end of the cycle, when the list of closed items is
>> quite long, then it does become a bit
> On Apr 11, 2018, at 4:58 PM, Peter Eisentraut
> wrote:
>
> On 4/11/18 10:53, Tom Lane wrote:
>> It's not that much work to move the items rather than remove them,
>
> Well, toward the end of the cycle, when the list of closed items is
> quite long, then it does become a bit of a burden to ca
Peter Eisentraut writes:
> On 4/11/18 10:53, Tom Lane wrote:
>> It's not that much work to move the items rather than remove them,
> Well, toward the end of the cycle, when the list of closed items is
> quite long, then it does become a bit of a burden to carefully cut and
> paste the item in the
On 4/11/18 10:53, Tom Lane wrote:
> It's not that much work to move the items rather than remove them,
Well, toward the end of the cycle, when the list of closed items is
quite long, then it does become a bit of a burden to carefully cut and
paste the item in the little browser window without maki
On 04/11/2018 10:06 AM, Alvaro Herrera wrote:
Andres Freund wrote:
On 2018-04-11 13:54:34 -0300, Alvaro Herrera wrote:
The other proposal was that we could have a simple web app to track open
items. After all, we now know what we need from it. A wiki page seems
more laborious. (The
Magnus Hagander wrote:
> (And of course, if we want to go in *any* direction away from the wiki,
> it's not going to happen in time for *this* release..)
Absolutely. But if we never start, it'll never get done.
--
Álvaro Herrerahttps://www.2ndQuadrant.com/
PostgreSQL Developmen
Andres Freund wrote:
> On 2018-04-11 13:54:34 -0300, Alvaro Herrera wrote:
> > The other proposal was that we could have a simple web app to track open
> > items. After all, we now know what we need from it. A wiki page seems
> > more laborious. (The commitfest app also sp
On Wed, Apr 11, 2018 at 6:57 PM, Andres Freund wrote:
> On 2018-04-11 13:54:34 -0300, Alvaro Herrera wrote:
> > The other proposal was that we could have a simple web app to track open
> > items. After all, we now know what we need from it. A wiki page seems
> >
On 2018-04-11 13:54:34 -0300, Alvaro Herrera wrote:
> The other proposal was that we could have a simple web app to track open
> items. After all, we now know what we need from it. A wiki page seems
> more laborious. (The commitfest app also sprung from a wiki page.)
Growing a numb
Jonathan S. Katz wrote:
> During some RMT discussions I had proposed formatting the open items
> into a table on the Wiki page with some useful info to help track the status
> and surface the necessary info to track down the open item.
The other proposal was that we could have a simpl
se to update the wiki page
> at all, or decide to remove entries rather than move-and-add-a-link,
> we're not coming out ahead.
>
> I'm not particularly wedded to the above idea; I'm just proposing it
> as a compromise solution.
During some RMT discussions I had propo
Robert Haas writes:
> On Wed, Apr 11, 2018 at 10:53 AM, Tom Lane wrote:
>> What *does* take time is adding a link to the commit, so I'd happily
>> drop that step. As Peter says, you can usually look in the commit
>> log if you care.
> The trouble is that sometimes it's not very obvious which co
On Wed, Apr 11, 2018 at 10:53 AM, Tom Lane wrote:
> Ashutosh Bapat writes:
>> On Wed, Apr 11, 2018 at 6:53 PM, Peter Eisentraut
>> wrote:
>>> Do people find it useful to move the resolved items to a separate
>>> section on the page, instead of just removing them? I'm not sure that
>>> the resol
Ashutosh Bapat writes:
> On Wed, Apr 11, 2018 at 6:53 PM, Peter Eisentraut
> wrote:
>> Do people find it useful to move the resolved items to a separate
>> section on the page, instead of just removing them? I'm not sure that
>> the resolved sections are useful, compared to just using the git lo
On Wed, Apr 11, 2018 at 6:53 PM, Peter Eisentraut
wrote:
> On 2/18/18 22:42, Michael Paquier wrote:
>> Okay, I have created a skeleton of page here:
>> https://wiki.postgresql.org/wiki/PostgreSQL_11_Open_Items
>> Feel free to add any bugs or issues related to v11 that need to be
>> tracked before
On 2/18/18 22:42, Michael Paquier wrote:
> Okay, I have created a skeleton of page here:
> https://wiki.postgresql.org/wiki/PostgreSQL_11_Open_Items
> Feel free to add any bugs or issues related to v11 that need to be
> tracked before the release.
Do people find it useful to move the resolved item
On Fri, Feb 09, 2018 at 11:37:52AM +0530, Ashutosh Bapat wrote:
> On Fri, Feb 9, 2018 at 9:14 AM, Michael Paquier wrote:
>> Are there any objections in creating a wiki page to track all those bugs
>> and issues? We don't want to lose track of all that.
>
> +1.
Okay, I have created a skeleton of
On Fri, Feb 9, 2018 at 9:14 AM, Michael Paquier wrote:
> Hi all,
>
> I begin seeing bugs related to new features of v11 popping up around,
> like this one for procedures:
> https://www.postgresql.org/message-id/CAFj8pRDxOwPPzpA8i%2BAQeDQFj7bhVw-dR2%3D%3DrfWZ3zMGkm568Q%40mail.gmail.com
>
> Are ther
Hi all,
I begin seeing bugs related to new features of v11 popping up around,
like this one for procedures:
https://www.postgresql.org/message-id/CAFj8pRDxOwPPzpA8i%2BAQeDQFj7bhVw-dR2%3D%3DrfWZ3zMGkm568Q%40mail.gmail.com
Are there any objections in creating a wiki page to track all those bugs
and
44 matches
Mail list logo
