According to the postgres 7 docs:
By default, Postgres executes transactions in unchained mode (also
known as “autocommit” in other database systems). In other words, each
user statement is executed in its own transaction and a commit is
implicitly performed at the end of the statement (if
Forest Wilkinson writes:
Does this mean that when I call a function I wrote, which is composed
of several queries, each of those queries will be executed in its own
transaction?
No
Or, will the statement containing the function call be executed in its
own transaction, thereby including
John Hasler wrote:
Carolyn Wong writes:
This program seems to use a lot of the memory on the linux server, and
the memory doesn't seem to be released at the end of execution.
Are you quite certain that this is actually what is happening? Linux
memory usage can be confusing.
I run
Hi all,
Hi all,
Before all, a little (off-topic) comment:
It's been my experience that Win32 ODBC does not drop
connections until the database client is closed (e.g. MS
Access is shut down).
"There is some things that only Micro$oft can do for you..."
Ok. Let's work.
