Re: damage control mode - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: damage control mode
Date
Msg-id 4B6F24A4.2020700@agliodbs.com
Whole thread Raw
In response to Re: damage control mode  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: damage control mode
Re: damage control mode
Re: damage control mode
List pgsql-hackers
Robert,

> As between the two, I get the feeling that there is more interest in
> writeable CTEs.  But that impression might be wrong, since it's an
> unscientific recollection of discussions on -hackers; which are
> themselves not representative of anything.

Writeable CTE is definitely the bigger feature.  Effectively, it allows
people to do in a single query data-transformation operations which
would have taken a stored procedure before.  Think of it as comparable
to the introduction of callbacks in Perl for coolness.

> I have not looked at the window functions patch at all, and I haven't
> looked at the latest version of writeable CTEs, either.  I will try to
> spend some time on it in the next couple of days.  My feeling about
> the last version is that it lacked a lot in the documentation
> department, and also in the comments department.  Since I don't know
> that code very well, that made it hard for me to assess technical
> correctness.

Hmmm, that's potentially lethal.  David Fetter has been doing a lot of
presentations on the feature; surely he could turn them into some
documentation?  David?

--Josh Berkus


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Hot standby documentation
Next
From: Andres Freund
Date:
Subject: Small Bug in pgstat display during recovery conflict resolution