Hello
I am working on plpgsql_check and I would to write a protection against
repeated check - so I need to mark a compiled (cached) function. Now,
plpgsql extension can store own data to exec state, and I would to some
similar for plpgsql_function. I believe so it can be useful for any plpgsql
Pavel Stehule escribió:
Hello
I am working on plpgsql_check and I would to write a protection against
repeated check - so I need to mark a compiled (cached) function. Now,
plpgsql extension can store own data to exec state, and I would to some
similar for plpgsql_function. I believe so it
2013/12/31 Alvaro Herrera alvhe...@2ndquadrant.com
Pavel Stehule escribió:
Hello
I am working on plpgsql_check and I would to write a protection against
repeated check - so I need to mark a compiled (cached) function. Now,
plpgsql extension can store own data to exec state, and I would
Pavel Stehule pavel.steh...@gmail.com writes:
Requested feature doesn't help me implement this concept 100%, but helps
with check If I worked with some instance of function or not. And inside
core a implementation is cheap. Outside core it is a magic with hash and
checking transaction id
2013/12/31 Tom Lane t...@sss.pgh.pa.us
Pavel Stehule pavel.steh...@gmail.com writes:
Requested feature doesn't help me implement this concept 100%, but helps
with check If I worked with some instance of function or not. And inside
core a implementation is cheap. Outside core it is a magic
On Wed, Jan 1, 2014 at 12:52 AM, Pavel Stehule pavel.steh...@gmail.com wrote:
2013/12/31 Alvaro Herrera alvhe...@2ndquadrant.com
I'm not sure I understand this. Do you want to avoid running the
checker if a previous run was seen as successful and function has not
changed? Suppose the
