During the execution of ProcessUtility() function in
/src/backend/xxx/utility.c,
the CreateStmt node type is processed to create a table.
Is there a global function in the context of the backend process that
will deliver what the current database and schema names?
The querystring cannot be
instead of patching the statically
compiled binary to simulate the triggers?
Cheers,
marco
On 9/21/2012 10:15 AM, Heikki Linnakangas wrote:
On 21.09.2012 17:58, m...@rpzdesign.com wrote:
During the execution of ProcessUtility() function in
/src/backend/xxx/utility.c,
the CreateStmt node type
will not even try
to contribute this work, unless someone wants it.
marco
On 9/21/2012 1:19 PM, Andres Freund wrote:
On Friday, September 21, 2012 08:12:26 PM m...@rpzdesign.com wrote:
Heikki:
Thanks for the response. I am writing an external replication engine
and putting hooks
subject
indeed.
I want CLOUD behavior without CLOUD prices.
Anybody who is working on the 9.3 COMMAND TRIGGER, drop me a note if you
wish.
marco
On 9/21/2012 3:41 PM, Andres Freund wrote:
Hi,
On Friday, September 21, 2012 11:06:46 PM m...@rpzdesign.com wrote:
Thanks for the link on the GIT
Andres, nice job on the writeup.
I think one aspect you are missing is that there must be some way for
the multi-masters to
re-stabilize their data sets and quantify any data loss. You cannot do
this without
some replication intelligence in each row of each table so that no
matter how
have not seen anybody request my hook code but a few have
responded that the are working
on things in the code base, release date unknown.
Cheers,
marco
On 9/24/2012 10:20 AM, Dimitri Fontaine wrote:
m...@rpzdesign.com m...@rpzdesign.com writes:
You may want to consider changing the command
replication needs
and async for all the master - master stuff.
cheers,
marco
On 9/24/2012 9:44 PM, Amit Kapila wrote:
On Monday, September 24, 2012 9:08 PM m...@rpzdesign.com wrote:
What a disaster waiting to happen. Maybe the only replication should be
master-master replication
so there is no need
, likely
because
they do not have a single db engine that meets all the requirements like PG.
marco
On 9/25/2012 5:10 PM, John R Pierce wrote:
On 09/25/12 11:01 AM, m...@rpzdesign.com wrote:
At some point, every master - slave replicator gets to the point
where they need
to start thinking
Josh:
The good part is you are the first person to ask for a copy
and I will send you the hook code that I have and you can be a good sport
and put it on GitHub, that is great, you can give us both credit for a
joint effort, I do the code,
you put it GitHub.
The not so good part is that the
I have been working on external replication on Postgresql 9.2 for a
little while
(with too many interruptions blocking my progress!)
Who knows a good utility to aggressively analyze
and recover Postgresql Databases?
It seems the standard reply that I see
is Make regular backups, but that
10 matches
Mail list logo
