David E. Wheeler
David E. Wheeler
Looks okay to me, though I agree that it could get annoying if the output of `pg_get_constraintdef` changes between releases.
Agreed, but maybe check with [pgsql-hackers](https://www.postgresql.org/list/pgsql-hackers/).
Oh well perhaps we're missing `has_pk(:schema, :table)`. If we had it you could make sure it's called instead of `has_pk(:schema, :desc)` by specifying the type: ``` sql SELECT has_pk('utility', 'eqpt_model_info'::name);...
> Would that fill in the missing :desc like SELECT has_pk('eqpt_model_info');? Yes, exactly.
No, I think that would be fine, as long as we updated `compat/install-8.4.patch` to switch it back to `NAME[]`.
pgTAP has patch files for support back to 8.1. I dropped 8.0 back in Nov 2011, so I'd say we could start dropping the other 8.x versions. Hasn't really been...
PGXN supports only semantic versions, so 1.001 is not allowed.
Sorry, was reading too quickly. Please don't change its return value, that would break compatibility. The value is set by the `$NUMVERSION` variable in the Makefile. I think the idea...
Sure, makes sense. Care to submit a pull request?
Jesus, trigger parsing code? In PL/pgSQL? o_O