Does anyone have a concise way of doing $SUBJECT?
Best,
Nathan
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
> Following the formula outlined
> in http://www.postgresql.org/docs/8.3/static/row-estimation-examples.html
> Both gradrate 10 and gradrate 11 would fall in the first bucket.
> Shouldn't the row estimation be:
> (11 - 8) / (33 - 8) / 10 * 1302 = 15.624
> and
> (10 - 8) / (33 - 8) / 10 * 1302 = 10.
>
> There is reference to slides with some
> frequency though, are they available somewhere?
>
Ya.
http://encodestatistics.org/publications/statistics_and_postgres.pdf
Is there a better place for this?
-Nathan
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make chang
>
> variant association phenotype
> --- --- -
> variant_id - variant_id +--- phenotype_id
> genome_id phenotype_id -+ short_descr
> strand origin_id (i.e., who)
>> Will there be a saved version of this (SFPUG talk) available for later
>> viewing? Don't
>> make me choose between steak and beer and postgres. 8(
>
> Yes! I'll announce it here when it's available.
>
Is there any update on this?
-Nathan
--
Sent via pgsql-general mailing list (pgsql-genera
> I have a query that takes 2 sec if I run it from a freshly restored dump.
> If I run a full vacuum on the database it then takes 30 seconds.
What do the two plans look like? Can you post the explains?
-Nathan
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make chang
Because people can be smarter about the data partitioning.
Consider a table of users. Some are active, most are not. The active
users account for nearly all of the users table access, but I still
(occasionally) want to access info about the inactive users.
Partitioning users into active_users and
Hi,
I just created a new column on a relatively large table (~ 2 mil rows over
400 mb in tablesize) and am trying to populate it from another much smaller
table by using an update query .
The purpose of the query to set a bool flag if the user for the action on
table1 is the last user, as determi
