Re: [PATCH] reloptions - RELOPT_KIND_ALL

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] reloptions - RELOPT_KIND_ALL
Date: 2009-01-23 15:19:37
Message-ID: 5238.1232723977@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> writes:
> Alvaro Herrera pe v p 23. 01. 2009 v 11:04 -0300:
>> Do you have an example use case for this?

> I use it in my space reservation patch. I going to send it soon.

Haven't we been over that ground already? A user-settable reloption
is not a reasonable solution to a space-reservation problem. The
potential for errors of commission and omission is too great.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2009-01-23 15:28:13 Re: Controlling hot standby
Previous Message Amit Gupta 2009-01-23 15:19:23 Re: Table Partitioning Feature