Thread: Help with 9.5 feature wiki page
Hi all, I've written a "What's new in PostgreSQL 9.5" page on the wiki, but I'd like some help. https://wiki.postgresql.org/wiki/What%27s_new_in_PostgreSQL_9.5 As you can see, there's some sections without content yet, and the rest may need tidy-up, simplifying, clarifying or correcting. So if anyone's up for helping out, please follow the link above and go edit. Thanks Thom
On Wed, May 20, 2015 at 7:36 AM, Thom Brown <thom@linux.com> wrote: > So if anyone's up for helping out, please follow the link above and go edit. Due to some MediaWiki weirdness, I cannot login to edit it. I can do so on other pages, but, for whatever reason, not on this particular page. I see a 403 forbidden error upon attempting to do so. I can successfully login on other pages using my community account, but then when I navigate back to this page MediaWiki is convinced that I am not logged in. I have experienced weirdness like this with MediaWiki before, and reported it to www-*. -- Regards, Peter Geoghegan
On Wed, May 20, 2015 at 7:52 PM, Peter Geoghegan <peter.geoghegan86@gmail.com> wrote: > Due to some MediaWiki weirdness, I cannot login to edit it. BTW, I wanted to edit the description of UPSERT. It's not true that the use of a CTE can be considered a workaround. That pattern can result in a spurious duplicate violation error with concurrent upserters, and so I'd definitely discourage it. The only workarounds that are robust involve subtransactions, like the plpgsql example in the docs, and there is no declarative way to do that. You need to catch a duplicate violation and retry to get a robust insert-or-update outcome. -- Regards, Peter Geoghegan
On Thu, May 21, 2015 at 12:07 PM, Peter Geoghegan <peter.geoghegan86@gmail.com> wrote: > On Wed, May 20, 2015 at 7:52 PM, Peter Geoghegan > <peter.geoghegan86@gmail.com> wrote: >> Due to some MediaWiki weirdness, I cannot login to edit it. > > BTW, I wanted to edit the description of UPSERT. It's not true that > the use of a CTE can be considered a workaround. That pattern can > result in a spurious duplicate violation error with concurrent > upserters, and so I'd definitely discourage it. The only workarounds > that are robust involve subtransactions, like the plpgsql example in > the docs, and there is no declarative way to do that. You need to > catch a duplicate violation and retry to get a robust insert-or-update > outcome. Perhaps adding this link from the docs mentioning merge_db() would be nice (cannot do it myself because of access forbidden with 403 when attempting to login): http://www.postgresql.org/docs/9.4/static/plpgsql-control-structures.html -- Michael
On 05/21/2015 04:52 AM, Peter Geoghegan wrote: > On Wed, May 20, 2015 at 7:36 AM, Thom Brown <thom@linux.com> wrote: >> So if anyone's up for helping out, please follow the link above and go edit. > > Due to some MediaWiki weirdness, I cannot login to edit it. I can do > so on other pages, but, for whatever reason, not on this particular > page. I see a 403 forbidden error upon attempting to do so. I can > successfully login on other pages using my community account, but then > when I navigate back to this page MediaWiki is convinced that I am not > logged in. > > I have experienced weirdness like this with MediaWiki before, and > reported it to www-*. yeah this is partly a known issue - certain pages on the wiki (like thos one that has a ' in the url which urlencoding) wont allow you to log in. It is new however that you can't login elsewhere and simply navigate to the affected page - I just tested this and it works fine that way for me, are you really sure this does not work? Stefan
On Wed, May 20, 2015 at 10:46 PM, Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> wrote: > yeah this is partly a known issue - certain pages on the wiki (like thos > one that has a ' in the url which urlencoding) wont allow you to log in. > It is new however that you can't login elsewhere and simply navigate to > the affected page - I just tested this and it works fine that way for > me, are you really sure this does not work? I tried again just now, on the page that was problematic before, and I was immediately logged on without even having to authenticate. I definitely had the problem that I described, but as always when the Wiki is acting up, it comes and goes. Anyway, I made the modification I wanted to make. -- Regards, Peter Geoghegan
On May 21, 2015 7:46 AM, "Stefan Kaltenbrunner" <stefan@kaltenbrunner.cc> wrote:
>
> On 05/21/2015 04:52 AM, Peter Geoghegan wrote:
> > On Wed, May 20, 2015 at 7:36 AM, Thom Brown <thom@linux.com> wrote:
> >> So if anyone's up for helping out, please follow the link above and go edit.
> >
> > Due to some MediaWiki weirdness, I cannot login to edit it. I can do
> > so on other pages, but, for whatever reason, not on this particular
> > page. I see a 403 forbidden error upon attempting to do so. I can
> > successfully login on other pages using my community account, but then
> > when I navigate back to this page MediaWiki is convinced that I am not
> > logged in.
> >
> > I have experienced weirdness like this with MediaWiki before, and
> > reported it to www-*.
>
>
> yeah this is partly a known issue - certain pages on the wiki (like thos
> one that has a ' in the url which urlencoding) wont allow you to log in.
> It is new however that you can't login elsewhere and simply navigate to
> the affected page - I just tested this and it works fine that way for
> me, are you really sure this does not work?
>
Fwiw, I believe the pages that mostly experience this problem are the ones that have a single quote in the page title (in this case, "what's"). That confuses the hell out of mediawiki. It might be a good idea to try to avoid such page titles of possible (and no, I don't think there is a way to make it forbidden..)
/Magnus
On 21 May 2015 at 04:07, Peter Geoghegan <peter.geoghegan86@gmail.com> wrote: > On Wed, May 20, 2015 at 7:52 PM, Peter Geoghegan > <peter.geoghegan86@gmail.com> wrote: >> Due to some MediaWiki weirdness, I cannot login to edit it. > > BTW, I wanted to edit the description of UPSERT. It's not true that > the use of a CTE can be considered a workaround. That pattern can > result in a spurious duplicate violation error with concurrent > upserters, and so I'd definitely discourage it. The only workarounds > that are robust involve subtransactions, like the plpgsql example in > the docs, and there is no declarative way to do that. You need to > catch a duplicate violation and retry to get a robust insert-or-update > outcome. I'd still regard it as a workaround, just with concurrency risks. But perhaps it's best to remove any mention of a workaround altogether. -- Thom
On Wed, May 20, 2015 at 07:52:47PM -0700, Peter Geoghegan wrote: > On Wed, May 20, 2015 at 7:36 AM, Thom Brown <thom@linux.com> wrote: > > So if anyone's up for helping out, please follow the link above and go edit. > > Due to some MediaWiki weirdness, I cannot login to edit it. I can do > so on other pages, but, for whatever reason, not on this particular > page. I see a 403 forbidden error upon attempting to do so. I can > successfully login on other pages using my community account, but then > when I navigate back to this page MediaWiki is convinced that I am not > logged in. When I ran into this issue, the following worked for me. - Go to the problem page. - Click "Main Page". - Log in as usual. - Use the back button to return to the page. - Reload the page > I have experienced weirdness like this with MediaWiki before, and > reported it to www-*. It's a little hokey, but I did manage to edit the page this way. Cheers, David. -- David Fetter <david@fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fetter@gmail.com Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate