> From: Thomas Munro [mailto:thomas.mu...@enterprisedb.com]
> > The file xact.c contains references to sub-transactions (subxact) and
> > transaction nesting level, but no obvious documentation about what
> > these correspond to in SQL. A search shows that plpython supports
> > something called “p
> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
> >> The file xact.c contains references to sub-transactions (subxact) and
> >> transaction nesting level, but no obvious documentation about what
> >> these correspond to in SQL.
>
> > Subtransactions are used to implement SAVEPOINT, and also BEGIN blo
> ow...@postgresql.org] On Behalf Of Tom Lane
> > Are there specific requirements or things to do/avoid in order to use
> > subtransactions (at the PL API level)?
>
> There isn't, currently, any very hard-and-fast rule about what APIs
> extensions should use or not use. My advice is to borrow fre
Windows 7 vs 10 makes no odds here. What matters is whether your Postgres or R
installations are x64 or x86.
Any x64 Windows can run x64 or x86 software perfectly happily, but you can’t
mix a DLL with an EXE of a different flavour. They have to match.
Regards
David M Bennett FACS
> Well, getting so that we can at least compile in both systems would
> certainly increase the chances of somebody being willing to work on
> such a design.
>From my particular perspective it would be enough if all the internal headers
>(that one needs to use in writing server-side extensions)
> > From my particular perspective it would be enough if all the
> internal
> > headers (that one needs to use in writing server-side extensions)
> were
> > completely usable in C++.
>
> That should already be the case. There's even a dirty hack^WWscript
> that checks that that remains the case
>
