Re: pg_upgrade from 9.4 to 10.4

Bruce Momjian writes: > On Fri, Aug 3, 2018 at 04:56:32PM -0400, Bruce Momjian wrote: >> On Fri, Aug 3, 2018 at 01:55:04PM -0400, Tom Lane wrote: >>> Right now is probably not a good time to fix this, but it seems like >>> something that could be improved. I'd be kind of inclined to remove >>>

Re: pg_upgrade from 9.4 to 10.4

On Fri, Aug 3, 2018 at 04:56:32PM -0400, Bruce Momjian wrote: > On Fri, Aug 3, 2018 at 01:55:04PM -0400, Tom Lane wrote: > > Bruce Momjian writes: > > > The comment at the top of src/port/system.c explains why we need those > > > quotes. Spaces was not the issue. > > > > So, while starting to

Re: Draft release notes are up

On Aug 4, 2018, at 1:17 PM, Jonathan S. Katz wrote:On Aug 4, 2018, at 12:17 PM, Jonathan S. Katz wrote:On Aug 4, 2018, at 12:11 PM, Tom Lane wrote:"Jonathan S. Katz" writes:[ s/interruptable/interruptible/ ]Hu

Re: Draft release notes are up

> On Aug 4, 2018, at 12:17 PM, Jonathan S. Katz wrote: > > >> On Aug 4, 2018, at 12:11 PM, Tom Lane wrote: >> >> "Jonathan S. Katz" writes: >>> [ s/interruptable/interruptible/ ] >> >> Huh ... I hadn't actually known that the two forms weren't more or less >> equally acceptable, but a bit o

Re: Stored procedures and out parameters

On Sat, Aug 04, 2018 at 07:03:47AM +0100, Shay Rojansky wrote: > > Shay>Npgsql currently always sends a describe as part of statement > > execution (for server-prepared messages the describe is done only once, at > > preparation-time). Vladimir, are you doing things differently here? > > > > The sa

Re: Draft release notes are up

> On Aug 4, 2018, at 12:11 PM, Tom Lane wrote: > > "Jonathan S. Katz" writes: >> [ s/interruptable/interruptible/ ] > > Huh ... I hadn't actually known that the two forms weren't more or less > equally acceptable, but a bit of dictionary-perusing says you're right. > Grep finds a couple of oth

Re: Draft release notes are up

"Jonathan S. Katz" writes: > [ s/interruptable/interruptible/ ] Huh ... I hadn't actually known that the two forms weren't more or less equally acceptable, but a bit of dictionary-perusing says you're right. Grep finds a couple of other "interruptable"s in our tree, both likely my fault.

Re: Draft release notes are up

> On Aug 3, 2018, at 6:15 PM, Tom Lane wrote: > > First cut at release notes for next week's minor releases is up at > > https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=c1455de2af2eb06ee493f9982f060ac7e571f656 > > If you prefer not to read XML markup, they should appear in t

Re: [report] memory leaks in COPY FROM on partitioned table

2018-08-03 12:38 GMT+09:00 Alvaro Herrera : > On 2018-Aug-03, Kohei KaiGai wrote: > >> 2018-08-02 5:38 GMT+09:00 Alvaro Herrera : >> > On 2018-Aug-01, Alvaro Herrera wrote: >> > >> >> Right, makes sense. Pushed that way. >> > >> > KaiGai, if you can please confirm that the pushed change fixes your

Conflict handling for COPY FROM

Hellow hackers, A few commitfest ago there was same effort to add errors handling to COPY FROM[1] and i see there that we already have infrastructure for supporting handling of unique violation or exclusion constraint violation error and I think it is independently useful too. Attached is a patch

Re: Stored procedures and out parameters

Shay Rojansky wrote: > In one way that's good, but I wonder how this squares with the following > written by David above: > > 1. A stored procedure should be able to return multiple resultsets with > different structures. > > 2. A stored procedure can decide dynamically of the structure of

Re: doc - improve description of default privileges

I have not found a convenient presentation of the default privileges for different objects, and how to display them (if possible, not always). The information is partly provided within the GRANT description, and not very explicit: eg it is said that owners have all possible perms, but which t