pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feed From: g.hintermayer@mail.inode.at
To: pgsql-interfaces@postgresql.org
Subject: libpgtcl modifications
Date: Thu, 08 Aug 2002 10:52:13 +0200
Message-ID: <E17cj1h-0004SY-00@e-mail.inode.at> (raw )
I hacked libpgtcl to get the following working:
> A broken backend connection trigers a notify event to the client (fixed
> notification string "connection_closed") so proper action can be taken to switch
> to another database server etc. Remember that this is event driven. If you have
> applications, that have idle database connections most of the time, you'll get
> immediate feedback of a dying server. Upon connection to the server issue a
> pg_notify for notify event "connection_closed" and whenever the backend crashes
> (which it does do in very very rare cases) you get an event driven recovery. (of
> course the Tcl-Event loop has to be processed). Issuing a notification
> "connection_closed" on a still working database could be used for switching to
> another db-server.
> I'd like to share my changes (because I don't want to apply them to every
> release). What's the way to go ?
Attached is a patch (hope I did it right ;-) )
Gerhard
--
Gerhard Hintermayer
http://www.inode.at/g.hintermayer
Attachments:
patch-notification.gz (text/plain, 1.3K) download
O= patch åXioã6ýìüÉÈÚª|ÈrÔRován6§³@QV¢l"²äP´[wÿÞ²\Mât»@ÀIÍp÷É<¡ìCYÀ$IåP°ô:*»zÅ)'«©ð«<LÏÒjÄ¿LÒªê³;ÒÇò)Fe½|ɧ$wÌhÓÚmîì6ÛP¯Õr¹ü¢x
ïé NkÛ»N<Ö)ÐÕxÓÙ±õ6¨ üýÐï
>ürr>ø|x~Ñ;9ýlãdÁOâ:p:üÀd/y÷¢jb'³ßßmØ¢WyPÚÛØú,êïåý8<äLü"ØìÀñåÑQüú~4¸òvõ+ïùÀU0r<ÔYSÃ?»S.Ð꫱ø\þ¯«_éÕBÕT&(ÇCÇ'ýÞû_ÍX,S@É'!saUééð-iù!½yL
ÏÌÒ¶£¶FÅÂÍÚeÖâm/x6kÉä¥%[ÅØãdÐgéºÛp_ÊXåï_w²óµîºv}»ñµ ô©à VQ^£RÕl
9â©*ºÆ'Â2 `çÆÏúøRlUô¤ÔãxRh¢·±Ý(Iò½^Yd;|ïô,ä1OG*Ð_CÄ,MCÄï(MC×Hô^=n:v³é.úk=q
ó¶òV±5EØÚRL#õÑëÏ'l9_N¶NÒ&R«u
ì.<gé4fæ½{ãUo¶RÂÏ'GýÞÑ¡Qð8sòQ
&h55¹dMüƹÑLUzµîëWÛqì¶ã®òÑ'LLÿIÄ_ê>X`̤~z¦_ÉÃ~Zé òB½ÑH¬ZªÞ:UÒ¼V,õ !Ê`ãd¦ø´`¦«èmè0ãBN½H³ûQByLxð(/&"A¤§í`µ[E¸·AnËno;«
âFb/æÈSÍÝ=ø24§¢ñ#æ `^P¦L@pñSø¥jáx:³^<ÊÛT_F_xq2E26ñ,Õízʦ¬éÈPW"ó¡*.ñ 0ÂÙÞÉ ç¿.fó±³óËJóÀÒIu -
±%~1å±$\-éSAÃá©ecwÜdST
2/jÛò¾`Qb`¿¹È7Æ@
[Þa5¨:Õao 㨠Oq4÷6äEÑõAúao¡]gÔeåX¤ïº(C-QgþAïÈç_
±bq O«¤×Ós7ßo÷ÑÍ7m·QËèf"¡1°èlT=;=kÐÑhúÕ$r®u Ûøvç¤*¦1Kn£m»ÍzFõ³QF
F_+Ø{«Úl`ðË]f¥Á¾¤ÆªuÁ²©cÁ°s,ö9å®¶wêdz»R=NðÆ´qò¤WÜþ£JÛjÙnk¹ï¼VtT§[5õ#^ûÂ1zþ!´Æ
cTè¦pâK¨· æî¶jæBÿÂö§.àm£YÛ9ü i·tfÒ>¢XÁzë#^x©/=uðkqÍSç/Sxcs
Åuùçùì1·¼³ú
ô|2Þöð,1ºÂ½òøl{¶ï
lqOÎõ¹<_}¨ÐÇlê!ßÿ¹CwTù»lÙßl¹ç»©
view thread (13+ messages) latest in thread
Message-ID: <E17cj1h-0004SY-00@e-mail.inode.at>
Permalink: ../E17cj1h-0004SY-00@e-mail.inode.at/
Also on: postgresql.org/message-id/E17cj1h-0004SY-00@e-mail.inode.at
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: g.hintermayer@mail.inode.at
Subject: Re: libpgtcl modifications
In-Reply-To: <E17cj1h-0004SY-00@e-mail.inode.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox