A simpler way to do this might be to only cache the list per query
context. In your IO functions, you could whack a pointer to your cache
onto fcinfo-flinfo-fn_extra, and the same flinfo gets passed in for
e.g. all output function calls for that column for that query, IIRC.
This was what I had
Rune Bromer [EMAIL PROTECTED] writes:
It sure is, but it seems to work now. It could be that the error isn't
persistant on a MacBook Pro as these have a x86 arch.
Exactly which version of readline (or, perhaps, libedit) are you using?
regards, tom lane
As far as memory management goes, do I just use hash_create() and assign
that pointer to fn_extra and at the end of the query it will be freed?
Or will it not be freed until this end of the transaction? I'm really
having trouble understanding the memory management issues with Postgres.
Greg
Greg Mitchell wrote:
Also, are there any ADTs like a hash-map or tree-map in the server
libraries (my background is C++ and am use to having std::map) or do I
need to role my own?
Look at the dynahash code. I just used it for the first time in a plperl
patch, and it's reasonably
Greg Mitchell [EMAIL PROTECTED] writes:
As far as memory management goes, do I just use hash_create() and assign
that pointer to fn_extra and at the end of the query it will be freed?
Or will it not be freed until this end of the transaction? I'm really
having trouble understanding the
Hi I've been making some changes to Postgres insertion method (InsertStmt)
and I'm trying to find out how much tuples are stored in one specific table
before the insertion of the next tuple, because of that will depend the
exact
insertion method that I will use...
I just really wanna know if
Clarence Gardner [EMAIL PROTECTED] writes:
That scenario seems quite simple, but I can't reproduce the deadlock with
this seemingly-identical sequence.
This is a bug in 8.1 and up. The reason you couldn't reproduce it is
that it requires a minimum of three transactions involved, two of which
On 11/17/06, Tom Lane [EMAIL PROTECTED] wrote:
we need a special case when we are already a member of the MultiXact:
fall through without trying to reacquire the tuple lock.
Small implementation detail: Also keep a count of how many times the same
session requested the same lock, and do not
Gurjeet Singh [EMAIL PROTECTED] writes:
On 11/17/06, Tom Lane [EMAIL PROTECTED] wrote:
we need a special case when we are already a member of the MultiXact:
fall through without trying to reacquire the tuple lock.
Small implementation detail: Also keep a count of how many times the same
On 11/17/06, Tom Lane [EMAIL PROTECTED] wrote:
Gurjeet Singh [EMAIL PROTECTED] writes:
Small implementation detail: Also keep a count of how many times the
same
session requested the same lock, and do not release the lock until he
requests same number of releases.
No need for that, because
Hi hackers,
The current usage PG_TRY() looks something like this:
... normal code ...
PG_TRY();
{
... code that might throw ereport(ERROR) ...
}
PG_CATCH();
{
... error recovery code ...
... plus anything that you wish to do even if an error wasn't
Gurjeet Singh [EMAIL PROTECTED] writes:
I propose a new constuct, PG_FINALLY.
I took a look through the existing uses of PG_CATCH, and found that in
the places where there is duplicate code between the normal and error
exits, it's usually just one or two lines. Where it's more than that,
it's
Markus Schiltknecht wrote:
Not mentioning that categorization doesn't help in clearing the
confusion. Just look around, most people use these terms. They're used
by MySQL and Oracle. Even Microsofts ActiveDirectory seems to have a
multi-master operation mode.
OK.
For example, Slony is
Any reason not to support renaming columns? Can this be added to TODO?
patch
Description: Binary data
--
Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
---(end of
Jim Nasby [EMAIL PROTECTED] writes:
Any reason not to support renaming columns? Can this be added to TODO?
Uh, we did that years ago.
regards, tom lane
---(end of broadcast)---
TIP 5: don't forget to increase your free
Tom Lane wrote:
Joachim Wieland [EMAIL PROTECTED] writes:
Current beta seems to have the 2006k version of the zic database. The
current
zic database is version 2006n however. Since this update does not include
source code but just data files I would vote to do the update in beta, what
Jim Nasby wrote:
Any reason not to support renaming columns? Can this be added to
TODO?
Upgrade to Postgres95.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Jim Nasby wrote:
As a less invasive alternative, I *think* you could create an SQL
function for casting text to int that treated '' as 0, and then
replace the built-in CAST with that.
Won't work. You need to replace the data type input function.
--
Peter Eisentraut
Ühel kenal päeval, R, 2006-11-17 kell 00:01, kirjutas Bruce Momjian:
Markus Schiltknecht wrote:
Not mentioning that categorization doesn't help in clearing the
confusion. Just look around, most people use these terms. They're used
by MySQL and Oracle. Even Microsofts ActiveDirectory seems
Ühel kenal päeval, R, 2006-11-17 kell 00:01, kirjutas Bruce Momjian:
Current version at:
http://momjian.us/main/writings/pgsql/sgml/failover.html
it refers to Warm Standby Using Point-In-Time
Recovery (http://momjian.us/main/writings/pgsql/sgml/warm-standby.html), maybe
its a good
20 matches
Mail list logo
