> I especially don't think that we should second-guess what the admin
> wants us to do by auto-killing backends that are still serving
> clients.
Sure. But it would be nice anyway if pg_ctl could do this with a
specific command line switch.
--
<< Tout n'y est pas parfait, mais on y honore ce
>
> > scan.c:2145: warning: `yy_fatal_error' defined but not used
>
> I have a sneakier idea to avoid the warning. [...]
>
> #define fprintf(file,fmt,msg) elog(FATAL, "%s", (msg))
Meaning no disrespect : yuck... IMHO this is asking for trouble
whenever someone decides to use another yacc. O
> This is flex, not yacc, and our lexer has been flex-only for a long
> time. It's possible that the hack would break in a future version
> of flex, but I doubt it. What else is a lexer going to use fprintf
> for?
Hmm, well of course you are right... (and I could use some sleep too
:-). OK, t
> yup :-) Maybe this could even be raised to the SQL level,
> so applications could use this ? I have not seen this elsewhere,
> but why actually not ?
Yes please :-) if someone is to code this quicker than me (I suppose
so, since I have other projects to deal with concurrently).
--
<< Tout
[ sorry to repost this, but I didn't receive my mail back... Anything
wrong with the mailserver ? ]
I am involved in a project of open-source, PostgreSQL-backed,
buzzword-compliant replication/high availability software that would
act as an SQL « one-to-many » gateway (but still in the design
> This 'pre-commit' 'really commit' two-step (get 'yer cowboy hats, right
> here) is what's needed, and is currently missing from pgsql.
Hello,
I'm very interested in this topic since I am involved in a
distributed, several-PostgreSQLs-backed, open-source,
buzzword-compliant database replic
