Hi,
The implementation of a set of hooks for efficient synchronous replication
without extensive patching of Postgresql source is now available at:
http://gorda.di.uminho.pt/community/
Note that this is far from a full replication product. It is made available
for early feedback by
Thank you for the comments.
First of all your patch does not conform with the project style. Please
have a look at how other files are indented, in particular regarding
brace position and ereport() arguments (any function arguments really,
but in ereport your problems are more visible). Also,
First of all your patch does not conform with the project style. Please
have a look at how other files are indented, in particular regarding
brace position and ereport() arguments (any function arguments really,
but in ereport your problems are more visible). Also, always use
ereport() for
You can find something to run triggers on commit at
http://gorda.di.uminho.pt/community/pgsqlhooks/
It also allows to define triggers on begin, startup and shutdown.
It works fine with triggers written in C.
A patch will be available soon in order to allow to writte triggers in
other languages
I fixed the patch and now it compiles in windows.
The first one did not compile because there were some problems in the
Makefile.
It is currently available for download at
http://gorda.di.uminho.pt/community/pgsqlhooks/.
Regards,
Alfranio
---(end of
Hi,
I running PostgreSQL 8.0.x with database that does not have foreign keys
and sometimes the following messages appears:
ERROR: deadlock detected
DETAIL: Process 10029 waits for ShareLock on transaction 65272; blocked
by process 32436.
Process 32436 waits for ShareLock on
HI,
I am running PostgreSQL 8.0.x with a database that does not have foreign
keys. However, sometimes the following messages appear:
deadlock detected: Process 10029 waits for ShareLock on transaction
65272; blocked by process 32436.Process 32436 waits for ShareLock on
transaction 65117;
Perhaps you are using SELECT FOR UPDATE?
I am not using SELECT FOR UPDATES...
Could it have another cause ?
---(end of broadcast)---
TIP 6: explain analyze is your friend
I am executing some stored procedures written in pl/pgsql
But wouldn't PostgreSQL show information per statement executed by the
functions ?
or SELECT func_with_side_effects() ?
-Mike
---(end of broadcast)---
TIP 5: don't forget to
I don't know if this the correct list to ask about implementation
details. If not, let me know.
Anyway, are there functions that return which processes or transactions
are holding locks in relations, tuples, etc ?
Best regards,
Alfranio
---(end of
Are there some sort of functions that I could use to know which process
has an exclusive lock on relations, pages, tuples, transactions,
etc... ?
Best regards,
Alfranio Junior
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
I mean, any C function.
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
Hi,
We have just released an add-on to PostgreSQL supporting the GORDA
Architecture and Programming Interface (GAPI). This opens up support for
DBMS
independent replication middleware, aimed at eager and multi-master
replication in clusters and WANs.
The implementation of the GAPI is achieved in
Markus Schiltknecht wrote:
Hi,
José Orlando Pereira wrote:
I would argue that people haven't been able to build production-grade
multi-master replication, in part, due to the barrier of not having a
standard database-agnostic API. :-)
In fact, the problem is not the lack of a standard API
Markus Schiltknecht wrote:
Hi,
Jose Orlando Pereira wrote:
Sorry, stuff was put twice in the zip file making it somewhat
confusing. It is in
postgresql-g-0.1/javasrc/GordaInterfaces/docs/gapi.pdf or directly on
the web site at http://gorda.di.uminho.pt/download/reports/gapi.pdf.
Thank
Markus Schiltknecht wrote:
I'm questioning if a replication system can be written by only using
triggers as hooks. AFAIK Slony-I uses triggers, so you can probably
better comment on problems or limitations using triggers. For me a
shared library with some hooks as C function calls seems a
Why reinvent the wheel for everything if there was an interface that
offered some of the needed functionality? Maybe PostgreSQL-R is simply
too deep in the database for any of this to be useful, but I'm 99%
certain that Slony could make use of some of this stuff, such as a hook
on tuples
Hi,
I have some questions on execution plans.
When are the following plans used ?
nodeFunctionscan.c nodeTidscan.c
In particular, is the plan nodeBitmapHeapscan.c always used along with
the nodeBitmapIndexscan.c ?
Please, let me know if there is a previous thread on this subject or any
Should these designations be more generic in case there are other uses
for enabling/disabling groups of triggers?
That would be fine with me, I just wasn't able to come up with any
sensible naming scheme other than replication related. Can you?
The best I could think of would be to create
19 matches
Mail list logo
