| Age | Commit message (Collapse) | Author |
|---|
|
Without it, the test can fail occasionally.
Reported by Peter Eisentraut.
|
|
Refactor some internals to make this possible. Mainly, FunctionCallInfo
is not available when validating, so avoid accessing that if not
required. Rename plproxy_compile() to plproxy_compile_and_cache() and
the previously internal fn_compile() to plproxy_compile(). This matches
their purpose better and allows the validator to call plproxy_compile()
without invoking execution-time dependent code.
Many error test cases have changed because the validator catches errors
when the function is created, not when it is called.
Raise the extension version to 2.5.1 to be able to upgrade from
non-validator installations.
|
|
|
|
|
|
|
|
|
|
Previously, as soon as cancel requests were send,
plproxy re-throwed the error, without waiting for
reaction from backend. Such behaviour creates
2 problems:
- If plproxy backend is closed immediately, the bouncer will
see plproxy close before cancel from backend, thus seeing
mid-tx close, thus dropping the connection.
- If new query comes in to plproxy backend, plproxy itself
will see dirty connection, closing it, thus also causing
close of server connection in bouncer.
In both cases it can cause server connection drop in pooler.
New behaviour of waiting query result should fix it.
|
|
On each call, recheck type relation rowstamp.
If it proves to be noticeable, we can use
syscache callback infrastructure for that,
but it will be much more complex.
|
|
|
|
|
|
- Use CREATE EXTENSION in 9.1+ tests
- set verbosity to 'terse' to have less noise
- Less messy Makefile rules
|
|
|
|
|
|
|
