Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 8157B2E1275 for ; Mon, 28 Jan 2008 20:16:04 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 99675-02-2 for ; Mon, 28 Jan 2008 20:15:59 -0400 (AST) Received: from mailsrv1.zmi.at (mailsrv1.zmi.at [212.69.162.198]) by postgresql.org (Postfix) with ESMTP id 772BC2E0D9B for ; Mon, 28 Jan 2008 20:15:59 -0400 (AST) Received: from mailsrv.i.zmi.at (85-125-129-125.neutorgasse.xdsl-line.inode.at [85.125.129.125]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mailsrv.i.zmi.at", Issuer "mailsrv.i.zmi.at" (not verified)) by mailsrv1.zmi.at (Postfix) with ESMTP id 5BFC99A7 for ; Tue, 29 Jan 2008 01:15:53 +0100 (CET) Received: from saturn.i.zmi.at (saturn.i.zmi.at [10.0.0.2]) by mailsrv.i.zmi.at (Postfix) with ESMTP id 101D2BEEA for ; Tue, 29 Jan 2008 01:15:10 +0100 (CET) From: Michael Monnerie Organization: it-management http://it-management.at To: pgsql-admin@postgresql.org Subject: Re: Syslog to postgresql - need peaks of 5.000/s Date: Tue, 29 Jan 2008 01:15:43 +0100 User-Agent: KMail/1.9.6 (enterprise 20070904.708012) References: <20080126185021.E912BBD5@mailsrv1.zmi.at> <479BB8F0.9090508@gmail.com> In-Reply-To: <479BB8F0.9090508@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart12026722.zRD2VvXrDF"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200801290115.50295@zmi.at> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/271 X-Sequence-Number: 28045 --nextPart12026722.zRD2VvXrDF Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Samstag, 26. Januar 2008 paul rivers wrote: > Anyway, that's my experience with this, hope it helps. Dear Paul, thanks a lot for the very detailed information. I'm more=20 relaxed now as it seems to be possible to do everything I wanted,=20 although I'm concerned that 5.000 inserted lines per second could be a=20 problem. I'll just start with a server and then see it's limits and=20 what more I need.=20 BTW, this information could be very interesting for you. According to=20 syslog, they will release the "direct syslog to postgresql" feature soon: http://www.balabit.com/network-security/syslog-ng/ You might not change the running process, but for a new implementation=20 this could make things much easier. mfg zmi =2D-=20 // Michael Monnerie, Ing.BSc ----- http://it-management.at // Tel: 0676/846 914 666 .network.your.ideas. // PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import" // Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4 // Keyserver: www.keyserver.net Key-ID: 1C1209B4 --nextPart12026722.zRD2VvXrDF Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQBHnnA2zhSR9xwSCbQRAjieAKC4vRQ28ZQkpzyTYrLdhMg5RAt2lgCeJT3T 01biv6t2xRrOTWG4/ca4Ef4= =WPZq -----END PGP SIGNATURE----- --nextPart12026722.zRD2VvXrDF--