Re: [GENERAL] how to avoid repeating expensive computation in select

: Re: [GENERAL] how to avoid repeating expensive computation in select To: Bob Price rjp_em...@yahoo.com Cc: Bill Moran wmo...@potentialtech.com, pgsql-general@postgresql.org Date: Thursday, February 3, 2011, 5:33 PM Bob Price rjp_em...@yahoo.com writes: If I set the COST of expensivefunc high

[GENERAL] how to avoid repeating expensive computation in select

I have been searching through the docs and mailing list and haven't found a way to do this, so I thought I would ask the community. I would like to know if there is a way in PostgreSQL to avoid repeating an expensive computation in a SELECT where the result is needed both as a returned value

[GENERAL] how to avoid repeating expensive computation in select

I have been searching through the docs and mailing list and haven't found a way to do this, so I thought I would ask the community. I would like to know if there is a way in PostgreSQL to avoid repeating an expensive computation in a SELECT where the result is needed both as a returned value

Re: [GENERAL] how to avoid repeating expensive computation in select

computation in select To: Bob Price rjp_em...@yahoo.com Cc: pgsql-general@postgresql.org Date: Thursday, February 3, 2011, 12:23 PM In response to Bob Price rjp_em...@yahoo.com: I have been searching through the docs and mailing list and haven't found a way to do this, so I thought I would ask