[HACKERS] Syntax error and reserved keywords

reserved keyword or something like that, other than nobody having been interested in doing the work? Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to you

Re: [HACKERS] Command Triggers, patch v11

Y case and in the specific command case has reduced. If you're saying to nothing, that's good news. Also, when calling the user's procedure from the same place in case of an ANY command trigger or a specific one it's then possible to just hand them over the exact same set of info (

Re: [HACKERS] Command Triggers, patch v11

that mean? > + cmd.objectname = NULL; /* composite object name */ User mapping and casts object names are composite, and I don't know how to represent that in a single text structure. > - DropPropertyStmt seems to be an unused leftover? Seems so, cleaned out. Regards, --

Re: [HACKERS] elegant and effective way for running jobs inside a database

be able > to respond to interrupts (if a NOTIFY comes in) and otherwise sleep > until the precalculated time that it next needs to launch a job. I think the ticker was proposed as a minimal component allowing to be developing the job system as an extension. Regards, -- Dimitri Fontaine h

Re: [HACKERS] Is it time for triage on the open patches?

27;m not willing to single-handedly (or even with > both hands) take on the task of reviewing everything that nobody else > is paying attention to. It seems like February has seen lots of participants distracted away from the commit fest, we should probably take this into account. Regards, -

Re: [HACKERS] Command Triggers, patch v11

of having Slony, Londiste and Bucardo able to use that and implement support for DLLs. I really want that to happen in 2012. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) T

Re: [HACKERS] Command Triggers, patch v11

sing plsh to go apt-get install an extension's package when you see the master just created it, so that your read only queries on the hot standby have a chance of loading the code you need. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- S

Re: [HACKERS] pg_prewarm

ntain the RAM content HOT on the standby in the same way we are able to maintain its data set on disk, though. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make ch

Re: [HACKERS] pg_prewarm

m alternate > relation forks is also supported, for completeness. Is it possible with your tool to snapshot the OS and PostgreSQL cache in order to warm an Hot Standby server? Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql

Re: [HACKERS] Review of patch renaming constraints

problem with in the previous round of testing. The regression test covering made me lazy enough not to retry the patch here, I trust Peter on testing his own work here :) I'll update my command trigger patch as soon as this one makes it in. Regards, -- Dimitri Fontaine http://2ndQuadrant.f

Re: [HACKERS] Command Triggers, patch v11

old on that myself (think pl/untrusted that would reach out to the OS and do whatever is needed there). You can even set the session_replication_role GUC to replica and only have the replica command triggers fired. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise,

Re: [HACKERS] Inline Extension

nning but obviously that won't happen given the other patches I'm playing with. This major redesign you're mentioning is a very good feedback already and will allow me to implement a non controversial patch for the next release. Thanks for dealing with the CF parts of that.

Re: [HACKERS] Finer Extension dependencies

Robert Haas writes: > Dimitri, are you going to post an updated patch for this CF? Yes, I intend to do that. Not sure about diverting from the command trigger patch while Thom is full speed on reviewing and helping me write the full covering test cases, though. Regards, -- Dimitri Fonta

Re: [HACKERS] elegant and effective way for running jobs inside a database

ho's using it in large scale production. While at it, if such a ticker could be used to implement job queues… https://github.com/markokr/skytools/tree/master/sql/ticker Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-ha

Re: [HACKERS] Trigger execution role

he function is SECURITY DEFINER. Also, the current patch makes command triggers superuser only. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subs

Re: [HACKERS] How to know a table has been modified?

ients. Problem is, implicit > table modifications done by CASCADE, TRIGGERS and so on. Some of that (triggers) is provided in the command triggers patch. The CASCADE not so much but your command trigger will get called on the top-level object. Regards, -- Dimitri Fontaine http://2ndQuadra

Re: [HACKERS] Command Triggers, patch v11

add it when rebasing once his patch has landed. I'm not sending a revised patch, please use the github branch if you want to do some more tests already, or ask me for either a new patch version or a patch-on-patch, as you see fit. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Command Triggers, patch v11

andlers of included procedure languages until they are able to init their language variables with the info. Then, do we want the command trigger functions to return type trigger or another specific type? I guess we want to forbid registering any function as a command trigger? Regards, -- Dim

Re: [HACKERS] Command Triggers, patch v11

ntries. It used to work this way in the patch, then when merging with the new remove object infrastructure I lost that ability. From the beginning Robert has been saying he didn't want that behavior, and Tom is now saying the same, IIUC. So we're back to one command, one

Re: [HACKERS] Command Triggers, patch v11

triggers here. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Command Triggers, patch v11

incremental patch attached for convenience. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support commit 301d8e58b6bfe89f35d82ad7a5216891f56c5d48 Author: Dimitri Fontaine Date: Sat Mar 3 15:18:59 2012 +0100 Fix RenameCmdTrigger(), per review. di

Re: [HACKERS] Command Triggers, patch v11

1 > > +1. I suggested the same thing a while back. Yeah, I know, I just wanted to hear from more people before ditching out a part of the work I did, and Thom was balancing in the opposite direction. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Forma

Re: [HACKERS] Command Triggers, patch v11

bit of copying and pasting should get > the job done. But had been (too easily) convinced not to take that route. You changed my mind already, I'll see about changing the code too tomorrow (a cold is having me out of steam for tonight). Regards, -- Dimitri Fontaine http://2ndQuadrant.f

Re: [HACKERS] Command Triggers, patch v11

fixing weird cases, getting there :) > I'm enjoying playing with this feature though btw. :) Thanks :) -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Command Triggers, patch v11

ages are that there's more maintenance overhead for > supporting multiple languages using special variables. Lots of, so I've been told, enough of it for not taking this choice seriously. I'll admit I didn't personally looked at what it would entail implementation wise. Reg

Re: [HACKERS] Command Triggers, patch v11

Thom Brown writes: > SELECT * INTO badname FROM goodname; Again, see Andres' patch about that. -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subs

Re: [HACKERS] Command Triggers, patch v11

hat received positive reviews by both Tom and Robert, once that's in I can easily add support for the command. Thanks Andres :) -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)

Re: [HACKERS] Command Triggers, patch v11

le for ALTER VIEW. Will add. > I'll hold off on testing any further until a new patch is available. That should happen soon. Ah, the joys of coding while kids are at home thanks to school holidays. I can't count how many times I've been killed by a captain and married to a princess

Re: [HACKERS] Finer Extension dependencies

that very topic to send a patch that just works, it seems. I'm going to fix that over the week-end. Thanks for your reviewing so far. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hacker

Re: [HACKERS] Runtime SHAREDIR for testing CREATE EXTENSION

d extension files so that we have a real per-database objects here, rather than per major version deployments that happen to be able to impact several clusters and databases in different and subtle ways. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Suppor

Re: [HACKERS] determining a type oid from the name

ame matches. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Extensions default full version (was: [HACKERS] Displaying accumulated autovacuum cost)

Greg Smith writes: > On 02/21/2012 04:44 PM, Dimitri Fontaine wrote: >> The solution would be to be able to create hstore 1.1 from 1.0 >> automatically and I sent over a very simple patch to do that, albeit >> after the deadline for the current CF (that's why it's

Re: [HACKERS] Displaying accumulated autovacuum cost

if people always should use the latest version. Maybe I'm missing something.. I think not that many people are using 9.1 in production already. Also bear in mind that the mechanism is not made only for contrib, it makes sense to ship in-house procedure code as an extension too. Regards,

Re: [HACKERS] Runtime SHAREDIR for testing CREATE EXTENSION

sn't play nicely with that setup. Please see the "inline extension" thread where answers to your problem have been discussed. https://commitfest.postgresql.org/action/patch_view?id=746 Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Sup

Re: [HACKERS] Future of our regular expression code

cence: http://swtch.com/plan9port/unix/ Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Notes about fixing regexes and UTF-8 (yet again)

h a mechanism be useful here? Would it be useful only when storing the regexp in a column somewhere then applying it in the query from there (so most probably adding a join or subquery somewhere)? Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support

Re: [HACKERS] MySQL search query is not executing in Postgres DB

n't you using to_char() if processing integers? Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support PS: having worked on telephone number prefix indexing and processing them as text, I might have a biased opinion. You don't add up phon

Re: [HACKERS] Triggers with DO functionality

ll out LANGUAGE plpgsql when we don't provide for PSM yet, so that we avoid some backwards compatibility problems down the road. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.o

Re: [HACKERS] Triggers with DO functionality

ten in? I'm not so sure about other function properties (SET, COST, ROWS, SECURITY DEFINER etc) because applying default and punting users to go use the full CREATE FUNCTION syntax would be a practical answer here. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Exper

Re: [HACKERS] Command Triggers

Robert Haas writes: > On Fri, Feb 17, 2012 at 10:42 AM, Dimitri Fontaine > wrote: >> Done.  Of course at the time the command trigger is created you can't >> distinguish if the CREATE INDEX command will be run CONCURRENTLY or not, >> so I've decided to issue

Re: [HACKERS] Command Triggers

Dimitri Fontaine writes: >>>> I think it would be better to bail on trying to use CREATE TRIGGER and >>>> DROP TRIGGER as a basis for this functionality, and instead create >>>> completely new toplevel statements CREATE COMMAND TRIGGER and DROP >>>&g

Re: [HACKERS] Command Triggers

ed yet, because you can't run DDL on the standby. Now that you mention it we should also provide support the GUC here and only fire the triggers matching it. I'm working on that now. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support --

Re: [HACKERS] Command Triggers

installcheck ok). Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Command Triggers

d both. What about putting those definitions into src/include/catalog/pg_cmdtrigger.h? Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscr

Re: [HACKERS] Command Triggers

gger, with the command name registered as "ANY", which is only safe as long as we don't provide a new SQL command whose command tag is ANY. We could decide that we want to name this magic ANY command "__ANY__", but it does not look like it fits the project usual naming

Re: [HACKERS] Command Triggers

Robert Haas writes: > On Thu, Feb 16, 2012 at 4:21 PM, Dimitri Fontaine > wrote: > That's certainly the easiest option. If you don't feel passionate > about spending a lot of energy figuring out how to make it secure, > then I suggest we just restrict it to superusers u

Re: [HACKERS] Command Triggers

elation and RelationData (resp. in src/include/utils/relcache.h and src/include/utils/rel.h), and only now I understand why :) Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)

Re: [HACKERS] Command Triggers

d contexts. So do you prefer lots of InitCommandContext() or adding another parameter to almost all functions called by standard_ProcessUtility()? > I am confused why this is adding a new file called dumpcatalog.c which > looks suspiciously similar to some existing pg_dump cod

Re: [HACKERS] [trivial patch] typo in doc/src/sgml/sepgsql.sgml

iver should then be able to both see it inline in the email and store it as a file. Tom uses inline attachments a lot, and apparently very few MUA are allowing both features on that (gnus is perfectly fine here). Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, F

Re: [HACKERS] Command Triggers

pace here, I guess, what else? I don't think I've added >> other shared objects in there yet. I share your analyze btw, will >> remove support. > > And databases. Right, on their way. >> something else, e.g. \dct would be your choice here? > > Yeah, probably.

Re: [HACKERS] Command Triggers

ing very simple for an initial > commit, and then add more stuff piece by piece. I had the feeling we did exactly that when reducing the API not to provide the parse tree nor the (rewritten) command string. I can see more features to drop off, like the ability to silently cancel a statement i

Re: [HACKERS] Finer Extension dependencies

nd forgot that I had to retest it all in between, which is what happen on a tight schedule and when working at night, I guess. So the best option I've found here had me add a new function in pg_depend.c, it's working as intended now. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr

Re: [HACKERS] psql tab completion for SELECT

al with, but it > could search through all the columns in database. > > That seems pretty useful, and it's more or less a one-line change, as in > the attached patch. Does that includes support for completing SRF functions in the FROM clause? Regards, -- Dimitri Fontaine http

Re: [HACKERS] Finer Extension dependencies

soon now. Please wait some more before punting this patch out of the current commit fest. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your

Re: [HACKERS] [GENERAL] pg_dump -s dumps data?!

a is true/false) constraint to filter the data. So I sure would appreciate being able to call that data rather than config, and to mark any table at once. If that doesn't need any pg_dump stretching I think providing that in 9.2 would be great. Regards, -- Dimitri Fontaine

Re: [HACKERS] Command Triggers

Dimitri Fontaine writes: >> Really I think there is not any single point where you can put the >> command-trigger hook and be done. In almost every case, the right >> place is going to be buried somewhere within the execution of the >> command. > > I'm finally

Re: [HACKERS] Inline Extension

per cluster) and the extension mechanism work per-database inside each cluster. But that's work for another release. Any comments before I spend time coding this? -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Inline Extension

led the 9.1 way, and vice versa. Don't let me speak about extension distribution facilities just now :) Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes

Re: [HACKERS] Inline Extension

it ought to dump them all, > not just some subset of them. Ok, but then, what about .so files? Wouldn't it make sense to be able to ship also the executable modules needed, and if not, why not? Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Su

Re: [HACKERS] Inline Extension

uppress this part of the dump? Makes sense, indeed. Well one could of course manually filter the dump object list too, of course… Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hack

Re: [HACKERS] Inline Extension

Or do you still want to insist that dump/restore shouldn't care about any extension, inline or not, and so you're given the responsibility to do the exact same thing yourself on the client side? Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Suppo

Re: [HACKERS] Inline Extension

;t want to be loading our .so from anywhere in the system and forcing them into a place owned by root is giving confidence, IIUC). With SQL only extensions, it's all non-superuser land anyway. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Suppor

Re: [HACKERS] Inline Extension

nd restore. Creating an inline extension means creating the .control and the .sql files in the extension_inline_directory, then running the current code. I can adapt the patch to this behavior this week. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support

Re: [HACKERS] Finer Extension dependencies

ecause extension feature kmeans > requires it > HINT: You can drop extension feature kmeans instead. Can you provide me the test case you've been using? That looks like a bug I need to fix, indeed (unless the problem lies in the test case, which would mean I need to tighten things som

Re: [HACKERS] automating CF submissions (was xlog location arithmetic)

Alex Shulgin writes: > Another idea: introduce some simple tag system in mails sent to -hackers > to be treated specially, e.g: [...] > How does that sound? Very much like what debbugs does already. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, For

Re: [HACKERS] automating CF submissions (was xlog location arithmetic)

nd some others will just make the content appear within the mail. It seems the vast majority falls into the unhelpful second category. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql

Re: [HACKERS] Finer Extension dependencies

u're right, I'll fix that in the next version of the patch. > So, that's pretty much I've reviewed quickly. I'll need more time to > look in detail, but I'd like more inputs for the high-level design and > direction. I hope to be answering to your ques

Re: [HACKERS] Command Triggers

alling the command trigger entry points to every supported command, I wanted to avoid that first. It's no big deal though, as the API is simple enough. Expect a new patch made this way early next week. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Forma

Re: [HACKERS] Inline Extension

g in, and I think we can bypass that problem entirely. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support diff --git a/contrib/hstore/Makefile b/contrib/hstore/Makefile index e9e5e53..2d624d3 100644 --- a/contrib/hstore/Makefile +++ b/contrib/hstore/Ma

Re: [HACKERS] Command Triggers

an extremely > limited amount of functionality, and then build on it. > Enhance-and-extend is so much easier than a monolithic code drop. I'm happy to read that, and I'm preparing next patch version (v6) with that goal in mind. Regards, -- Dimitri Fontaine http://2ndQuadrant.

Re: [HACKERS] Inline Extension

us to work on that this late, dunno. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Command Triggers

schema name (or null) and the object name (or null) as input parameters to the trigger's procedure. I'm now working on that and then the concurrency angle of the command triggers. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sen

Re: [HACKERS] Inline Extension

#x27;m understanding how alone I am here), let's hear from the field first. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Inline Extension

oyments where the sys admins are your colleagues. I've been told that's a smaller and smaller part of the database world though. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postg

Re: [HACKERS] Inline Extension

some other variant. Or some other means of easily deploying the files. An SQL connection is all you need if you're not shipping .so. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-ha

Re: [HACKERS] Command Triggers

for serial column "ab_foo-bar.id" NOTICE: snitch: CREATE SEQUENCE ERROR: unrecognized node type: 904 I'm not sure about the next step, and I'm quite sure I need to stop here for tonight. Any advice welcome, I'll be working on that again as soon as tomorrow. Regard

Re: [HACKERS] Command Triggers

s the cost of doing so acceptable? Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Command Triggers

Tom Lane writes: > Dimitri Fontaine writes: >> I still have some cleaning to do before to prepare the next patch >> version, such as documentation updating and dealing with rewrites of >> CHECK and DEFAULT column constraints in CREATE TABLE. I had to add >> support fo

Re: [HACKERS] Command Triggers

Dimitri Fontaine writes: > Robert Haas writes: >> But on the flip side, I think we're generally a bit more flexible >> about exposing things via C than through the procedural languages. > > Then as Andres proposed, a new function would be available to get the >

Re: [HACKERS] WIP patch for parameterized inner paths

releases now. > > Comments? Go Tom go ! :) Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] SKIP LOCKED DATA

e other uses. To attack this problem in PostgreSQL we also have PGQ, which is Skytools3 has support for cooperative consumers. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org

Re: [HACKERS] PL/Python result metadata

with the PL/Python API being a small layer on > top of SPI, and let the likes of plpydbapi handle the rest. I'm discovering that, and again, fair enough :) Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing

Re: [HACKERS] Command Triggers

ded trigger, but I'll admit I'm yet to code a trigger in C. Will look into that. Then as Andres proposed, a new function would be available to get the value, we're not changing the trigger procedure function API in case the language is C… Regards, -- Dimitri Fontaine http:

Re: [HACKERS] Multithread Query Planner

Frederico writes: > This means it's possible use threads? The short answer is “no”. -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscripti

Re: [HACKERS] Disabled features on Hot Standby

ict they'll get fixed pretty quickly. So this problem goes into the 9.2 Open Items list, right? It looks not tied to this particular commit fest. Also, with so many people involved, I think there shouldn't be any finger pointing here. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr

Re: [HACKERS] Command Triggers

you can't easily know in which order your hooks will get fired, contrary to triggers, and you can't even list the hooks. I fear that we won't be able to answer your need here in 9.2 though. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation

Re: [HACKERS] Command Triggers

proposed a public API and changing the parsetree stops being internal refactoring. The way around this problem is that if you want a command trigger in C, just write an extension that implements the Process Utility hook. Bonus, you can have that working with already released versions of PostgreS

Re: [HACKERS] Multithread Query Planner

tead of multiple processes for > backends because: I would only add that the backend code is really written in a process based perspective, with a giant number of private variables that are in fact global variables. Trying to “clean” that out in order to get to threads… wow. Regar

Re: [HACKERS] Standalone synchronous master

be demoted from sync variant, while not being really async ones. Maybe “eager” or some other term. It seems to me that would answer the OP use case and your remark here. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers

Re: [HACKERS] Disabled features on Hot Standby

appens to rely on I'm very sorry to read that, because I sure feel like that's exactly what us non commiters are asked to be doing when cooking any patch. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hac

Re: [HACKERS] Command Triggers

BEFORE-DROP, and > maybe even AFTER-ALTER triggers without exposing any parse tree > details. Please find attached v5 of the patch, with nodeToString() support removed. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support command-t

Re: [HACKERS] ERRCODE_READ_ONLY_SQL_TRANSACTION

ster when seeing that in a “proxy” of some sort. I felt that we were missing something simple here, but after review I think we finally have all the pieces to achieve that with current 9.2 code base in fact. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation

Re: [HACKERS] PL/Python result metadata

rable API as in psycopg or DB API http://initd.org/psycopg/docs/cursor.html You could expose a py.description structure? -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make

Re: [HACKERS] Command Triggers

ch in the current state of affairs (I saw no progress on the JSON data type and facilities) is very hard to imagine when you consider PLpgSQL. So unless I hear about a show stopper, I'm going to work some more on the command trigger patch where I still had some rough edges to polish. Regard

[HACKERS] Inline Extension

x27; with $pair$ CREATE OR REPLACE FUNCTION key(pair) RETURNS text LANGUAGE SQL AS 'SELECT ($1).k;'; CREATE OR REPLACE FUNCTION value(pair) RETURNS text LANGUAGE SQL AS 'SELECT ($1).v;'; CREATE OPERATOR %% (RIGHTARG = pair, PROCEDURE = key); CREATE OPERATOR %#

Re: [HACKERS] backup_label during crash recovery: do we know how to solve it?

parallel of running the base backup, which is only important if you don't have already some archiving in place. I guess that the dedicated subprocess doing the WAL copy could be enhanced to talk the wal streaming protocol when the server is recent enough. Regards, -- Dimitri Fonta

Re: [HACKERS] [RFC] grants vs. inherited tables

on't > see a way to do it in pl/pgsql. (Writing parser in plpgsql > for aclitemout() output does not count.) We solved that manually in https://github.com/slardiere/PartMgr, maybe you will find it useful for pre-9.2 releases. See function partition.grant() and partition.setgrant() in

Re: [HACKERS] sorting operators in pg_dump

Peter Eisentraut writes: > order, say, prefix, postfix, infix. > > (It might be surprising that something like this is necessary, but it > happens. ip4r for example contains operators with different fixnesses > (fixities?).) I think it's called “arity” :) Regards, -- D

Re: [HACKERS] contrib/README

Tom Lane writes: > I wonder whether it's time to drop that file altogether ... it served a > purpose back before we integrated contrib into the SGML docs, but now > I'm not quite sure why we should bother with it. I wonder if we shouldn't keep the file and have it just point to the relevant docum

Re: [HACKERS] Standalone synchronous master

s switch set, isn't it? Isn't that equivalent to setting synchronous_standby_names to '' and reloading the server? Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hacke

<    2   3   4   5   6   7   8   9   10   11   >