[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Prism continued
- Subject: Prism continued
- From: eugen at leitl.org (Eugen Leitl)
- Date: Thu, 13 Jun 2013 08:47:33 +0200
- In-reply-to: <CAHsqw9sivWnTeZ=76dDHFGJchJkGWaovK+C2k7STH7CgHNMwmw@mail.gmail.com>
- References: <[email protected]> <CAJXc8RKN7awhiYZ9Th6sa=+yrGcXvoayzBsrsYsjLZN3HJRGtA@mail.gmail.com> <CAPz7E52=1LE=JVo7W7Rwj4akq=qU5npnwfK6a--EVz_Lb0JxcA@mail.gmail.com> <CAPhg-wQv6e0NONDA+D3QG3J7fmzbo3D9_v9LqWDSpdoGpuKmTw@mail.gmail.com> <[email protected]> <CAHsqw9sivWnTeZ=76dDHFGJchJkGWaovK+C2k7STH7CgHNMwmw@mail.gmail.com>
On Wed, Jun 12, 2013 at 06:35:35PM -0700, Jonathan Lassoff wrote:
> In the PRISM context, I highly doubt their using Splunk for any kind
> of analysis beyond systems and network management. It's not good at
> indexing non-texty-things.
> What if you need to search for events that were geographically
> proximate to one another? That takes a special kind of index.
PostgreSQL has PostGIS, but I doubt it's high-performance.