Re: Pg 16: will pg_dump & pg_restore be faster?

2023-06-02 Thread Jonathan S. Katz
On 5/30/23 10:05 PM, David Rowley wrote: My understanding had been that concurrency was required, but I see the commit message for 00d1e02be mentions: Even single threaded COPY is measurably faster, primarily due to not dirtying pages while extending, if supported by the operating system (see

Re: Upgrading from 11 to 13

2021-04-01 Thread Jonathan S. Katz
On 4/1/21 6:06 PM, Bruce Momjian wrote: An explicit sentence stating that major upgrades can skip major versions is >> needed.  The document is written assuming the reading knows this, and just >> makes a few minor notes on the topic: >> e.g., "If you are upgrading across several major versions, be

Re: CVE-2019-9193 about COPY FROM/TO PROGRAM

2019-04-02 Thread Jonathan S. Katz
gt; wrote on 04/02/2019 01:05:01 AM: > > > > > From: Michael Paquier <mailto:mich...@paquier.xyz>> > > > To: "Jonathan S. Katz" <mailto:jk...@postgresql.org>> > > > Cc: Tom Lane mailto:t...@sss.pgh.pa.us>>

Re: CVE-2019-9193 about COPY FROM/TO PROGRAM

2019-04-02 Thread Jonathan S. Katz
On 4/2/19 1:05 AM, Michael Paquier wrote: > On Mon, Apr 01, 2019 at 10:04:32AM -0400, Jonathan S. Katz wrote: >> +1, though I’d want to see if people get noisier about it before we rule >> out an official response. >> >> A blog post from a reputable author who can spe

Re: CVE-2019-9193 about COPY FROM/TO PROGRAM

2019-04-01 Thread Jonathan S. Katz
> On Apr 1, 2019, at 9:55 AM, Tom Lane wrote: > > Magnus Hagander writes: >>> On Sat, Mar 30, 2019 at 10:16 PM Tom Lane wrote: >>> Yeah; this is supposing that there is a security boundary between >>> Postgres superusers and the OS account running the server, which >>> there is not. We could

Re: User documentation vs Official Docs

2018-07-16 Thread Jonathan S. Katz
> On Jul 16, 2018, at 8:08 PM, Alvaro Herrera wrote: > > On 2018-Jul-16, Joshua D. Drake wrote: > >> Think of this (if we can figure out how to pull this off): User on >> StackOverflow says, "How do I do X", someone answers with a direct >> link to a recipe on PostgreSQL.Org that tells them exa

Re: Code of Conduct plan

2018-06-08 Thread Jonathan S. Katz
> On Jun 8, 2018, at 4:46 AM, Simon Riggs wrote: > > On 6 June 2018 at 19:22, Tom Lane wrote: >> I wrote: >>> Yeah, somebody else made a similar point upthread. I guess we felt that >>> the proper procedure was obvious given the structure, but maybe not. >>> I could support adding text to cla

Re: Code of Conduct plan

2018-06-05 Thread Jonathan S. Katz
> On Jun 5, 2018, at 3:16 PM, Tom Lane wrote: > > Chris Travers writes: >> On Tue, Jun 5, 2018 at 8:42 PM, James Keener wrote: >>> The question is: how can you (honestly) make people feel like we'll take >>> complaints seriously, while also not allowing for the politics that I've >>> seen sur

Re: Code of Conduct plan

2018-06-05 Thread Jonathan S. Katz
> On Jun 5, 2018, at 12:32 PM, Tom Lane wrote: > > James Keener writes: >> I don't participate too much here, but I've never see a group implement >> a code of conduct go well. There’s also a lot of evidence to the contrary, where groups have successfully implemented CoCs as well by extension

Re: Code of Conduct plan

2018-06-04 Thread Jonathan S. Katz
> On Jun 4, 2018, at 7:23 PM, Tom Lane wrote: > > Vik Fearing writes: >> Also I think official text should have its own page on the website, >> rather than just be on the wiki. Hopefully that's already planned. > > Right; we'll mark the formal blessing of the text by moving it onto > the mai

Re: Code of Conduct plan

2018-06-04 Thread Jonathan S. Katz
> On Jun 4, 2018, at 6:41 PM, Tom Lane wrote: > > "Joshua D. Drake" writes: >> On 06/04/2018 01:46 PM, Tom Lane wrote: >>> ... The reason for this is an unfortunate situation that took place in >>> the FreeBSD community awhile back [1], wherein one community member was >>> abusing another via

Re: Code of Conduct plan

2018-06-03 Thread Jonathan S. Katz
> On Jun 3, 2018, at 7:08 PM, Gavin Flower > wrote: > > On 04/06/18 07:32, Adrian Klaver wrote: >> On 06/03/2018 11:29 AM, Tom Lane wrote: >>> Two years ago, there was considerable discussion about creating a >>> Code of Conduct for the Postgres community, as a result of which >>> the core tea

Re: New website

2018-04-20 Thread Jonathan S. Katz
> On Apr 20, 2018, at 2:57 PM, Adrian Klaver wrote: > > On 04/20/2018 11:33 AM, Jonathan S. Katz wrote: >>> On Apr 18, 2018, at 8:38 PM, Adrian Klaver >> <mailto:adrian.kla...@aklaver.com>> wrote: >>> >>> Clicking on the Mailing List l

Re: New website

2018-04-20 Thread Jonathan S. Katz
> On Apr 18, 2018, at 8:38 PM, Adrian Klaver wrote: > > Clicking on the Mailing List link on front page should take you to page that > includes the archives. We’ve added a button that brings you to the archives from the homepage. Thanks, Jonathan

Re: New website

2018-04-18 Thread Jonathan S. Katz
> On Apr 18, 2018, at 6:40 PM, Adrian Klaver wrote: > >> On 04/18/2018 03:07 PM, Peter Geoghegan wrote: >> On Wed, Apr 18, 2018 at 3:03 PM, Adrian Klaver >> wrote: >>> I would contact the Webmaster but Contact goes to a big image of an elephant >>> head. That is also where Downloads, Support an