El 31/10/14 a las 04:46, Jayadevan M escibió:
> Hi all,
>
> I am going through PostgreSQL documentation on how row estimation is
> done in PostgreSQL.
> http://www.postgresql.org/docs/current/static/row-estimation-examples.html
> There is a reference to cardinality (rel_cardinality) there. But tha
Hi all,
I am going through PostgreSQL documentation on how row estimation is done
in PostgreSQL.
http://www.postgresql.org/docs/current/static/row-estimation-examples.html
There is a reference to cardinality (rel_cardinality) there. But that is an
estimate of the number of rows in the table, right
2008/5/30 Merlin Moncure <[EMAIL PROTECTED]>:
> On Fri, May 30, 2008 at 11:43 AM, Clodoaldo
> <[EMAIL PROTECTED]> wrote:
>> What should be changed in the query planning configuration, if at all,
>> if a ultrafast solid state drive would be used to host a whole
>> database ? Specially if used in Rai
On Fri, May 30, 2008 at 2:55 PM, Clodoaldo
<[EMAIL PROTECTED]> wrote:
> 2008/5/30 Merlin Moncure <[EMAIL PROTECTED]>:
>> On Fri, May 30, 2008 at 11:43 AM, Clodoaldo
>> <[EMAIL PROTECTED]> wrote:
>>> What should be changed in the query planning configuration, if at all,
>>> if a ultrafast solid stat
On Fri, May 30, 2008 at 9:43 AM, Clodoaldo
<[EMAIL PROTECTED]> wrote:
> What should be changed in the query planning configuration, if at all,
> if a ultrafast solid state drive would be used to host a whole
> database ? Specially if used in Raid 0 configurations.
Well, random page cost should be
On Fri, May 30, 2008 at 11:43 AM, Clodoaldo
<[EMAIL PROTECTED]> wrote:
> What should be changed in the query planning configuration, if at all,
> if a ultrafast solid state drive would be used to host a whole
> database ? Specially if used in Raid 0 configurations.
random_page_cost can probably be
What should be changed in the query planning configuration, if at all,
if a ultrafast solid state drive would be used to host a whole
database ? Specially if used in Raid 0 configurations.
Regards, Clodoaldo Pinto Neto
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make
