Tom Lane wrote:
> I'm of the opinion that #2 is the lesser evil, but maybe I'm overly
> influenced by my Red Hat packaging responsibilities --- I'll personally
> have to spend time on a compatibility package if we go with #1.
> Other opinions out there?
>
> Also, if we do #2 it means that we have the option to resolve the
> contrib/txid mess by pushing txid into the core backend before beta2.
> Any votes pro or con on that?
>
>
>
#2 by all means. Post-beta initdb is mildly unfortunate; compatibility
packages are to be avoided far more.
+1 to put txid in core, where it belongs.
cheers
andrew
