Robert Haas robertmh...@gmail.com writes:
Discuss.
This thread badly needs a more informative Subject line.
But, yeah: do people think the referenced commit fixes a bug bad enough
to deserve a quick update release? If so, why? Multiple reports of
problems in the field would be a good reason,
On 03/12/2014 06:15 PM, Tom Lane wrote:
Robert Haas robertmh...@gmail.com writes:
Discuss.
This thread badly needs a more informative Subject line.
No kidding. Or at least a link for goodness sake. Although the
pgsql-packers list wasn't all that helpful either.
What I know is that we
Josh Berkus escribió:
On 03/12/2014 03:58 PM, Robert Haas wrote:
I don't like the idea of using reloptions to let people attach
arbitrary unvalidated settings to tables. I consider the way things
work with GUCs to be a bug, not a feature, and definitely not
something I want to propagate
* Tom Lane (t...@sss.pgh.pa.us) wrote:
This thread badly needs a more informative Subject line.
Agreed.
But, yeah: do people think the referenced commit fixes a bug bad enough
to deserve a quick update release? If so, why? Multiple reports of
problems in the field would be a good reason,
Joshua D. Drake wrote
On 03/12/2014 06:15 PM, Tom Lane wrote:
Robert Haas lt;
robertmhaas@
gt; writes:
Discuss.
This thread badly needs a more informative Subject line.
No kidding. Or at least a link for goodness sake. Although the
pgsql-packers list wasn't all that helpful either.
On 12 March 2014 22:58, Robert Haas robertmh...@gmail.com wrote:
I don't like the idea of using reloptions to let people attach
arbitrary unvalidated settings to tables.
I respect your opinion. If you disagree, don't use them. Same as is
possible for RULEs etc.
I consider the way things
On Wed, Mar 12, 2014 at 9:38 PM, Simon Riggs si...@2ndquadrant.com wrote:
On 12 March 2014 22:58, Robert Haas robertmh...@gmail.com wrote:
I don't like the idea of using reloptions to let people attach
arbitrary unvalidated settings to tables.
I respect your opinion. If you disagree, don't
Hi all,
Shouldn't the ALTER statements below raise an exception?
fabrizio=# CREATE TABLE foo(bar SERIAL PRIMARY KEY);
CREATE TABLE
fabrizio=# SELECT relname, reloptions FROM pg_class WHERE relname ~ '^foo';
relname | reloptions
-+
foo |
foo_bar_seq |
On 13 Mar 2014 01:36, Stephen Frost sfr...@snowman.net wrote:
* Tom Lane (t...@sss.pgh.pa.us) wrote:
This thread badly needs a more informative Subject line.
Agreed.
But, yeah: do people think the referenced commit fixes a bug bad enough
to deserve a quick update release? If so, why?
On Thu, Mar 13, 2014 at 12:16 AM, Robert Haas robertmh...@gmail.com wrote:
On Tue, Mar 11, 2014 at 3:53 AM, Amit Kapila amit.kapil...@gmail.com wrote:
Places where tuple info not available
LOG: process 5788 still waiting for ShareLock on transaction 679 after
1014.000
ms
CONTEXT: while
On 13 March 2014 02:14, Robert Haas robertmh...@gmail.com wrote:
I'm not sure why this is being blocked. This is a community
contribution that seeks to improve everybody's options. Blocking it
does *nothing* to prevent individual extensions from providing
table-level options - we give them
On Mon, Dec 9, 2013 at 11:27:28AM -0500, Robert Haas wrote:
On Thu, Dec 5, 2013 at 6:15 PM, Tom Lane t...@sss.pgh.pa.us wrote:
But the other usages seem to be in assorted utilities, which
will need to do it right for themselves. initdb.c's walkdir() seems to
have it right and might be a
101 - 112 of 112 matches
Mail list logo
