Re: [GENERAL] Caching and Blobs in PG? Was: Can PG replace redis, amqp, s3 in the future?

2017-05-07 Thread Steve Atkins
> On May 7, 2017, at 9:16 AM, Adam Brusselback > wrote: > > there's also pg_agent which is a cron-like extension, usually bundled with > pg_admin but also available standalone > > https://www.pgadmin.org/docs4/dev/pgagent.html > > > -- > john r pierce, recycling bits in santa cruz > > In

Re: [GENERAL] Caching and Blobs in PG? Was: Can PG replace redis, amqp, s3 in the future?

2017-05-07 Thread Adam Brusselback
> > there's also pg_agent which is a cron-like extension, usually bundled with > pg_admin but also available standalone > > https://www.pgadmin.org/docs4/dev/pgagent.html > > > -- > john r pierce, recycling bits in santa cruz > In addition to that, there is also jpgAgent: https://github.com/GoSim

Re: [GENERAL] Caching and Blobs in PG? Was: Can PG replace redis, amqp, s3 in the future?

2017-05-05 Thread Peter J. Holzer
On 2017-05-05 11:46:55 -0700, John R Pierce wrote: > On 5/5/2017 11:28 AM, Peter J. Holzer wrote: > > On 2017-05-04 23:08:25 +0200, Sven R. Kunze wrote: > > On 03.05.2017 12:57, Thomas Güttler wrote: > > Am 02.05.2017 um 05:43 schrieb Jeff Janes: > > No.

Re: [GENERAL] Caching and Blobs in PG? Was: Can PG replace redis, amqp, s3 in the future?

2017-05-05 Thread John R Pierce
On 5/5/2017 11:28 AM, Peter J. Holzer wrote: On 2017-05-04 23:08:25 +0200, Sven R. Kunze wrote: On 03.05.2017 12:57, Thomas Güttler wrote: Am 02.05.2017 um 05:43 schrieb Jeff Janes: No. You can certainly use PostgreSQL to store blobs. But then, you need to store the PostgreSQL data **somepla

Re: [GENERAL] Caching and Blobs in PG? Was: Can PG replace redis, amqp, s3 in the future?

2017-05-05 Thread Peter J. Holzer
On 2017-05-04 23:08:25 +0200, Sven R. Kunze wrote: > On 03.05.2017 12:57, Thomas Güttler wrote: > >Am 02.05.2017 um 05:43 schrieb Jeff Janes: > >>No. You can certainly use PostgreSQL to store blobs. But then, you > >>need to store the PostgreSQL data **someplace**. > >>If you don't store it in S3

Re: [GENERAL] Caching and Blobs in PG? Was: Can PG replace redis, amqp, s3 in the future?

2017-05-05 Thread Jeff Janes
On Wed, May 3, 2017 at 3:57 AM, Thomas Güttler wrote: > Am 02.05.2017 um 05:43 schrieb Jeff Janes: > >> On Sun, Apr 30, 2017 at 4:37 AM, Thomas Güttler < >> guettl...@thomas-guettler.de > >> wrote: >> >> Is is possible that PostgreSQL will replace these bu

Re: [GENERAL] Caching and Blobs in PG? Was: Can PG replace redis, amqp, s3 in the future?

2017-05-04 Thread Alan Hodgson
On Thursday 04 May 2017 14:47:54 John R Pierce wrote: > On 5/4/2017 2:28 PM, Alan Hodgson wrote: > > On Thursday 04 May 2017 14:21:00 John R Pierce wrote: > >> or EBS, and I've heard from more than a few people that EBS can be > >> something of a sand trap. > > > > Sorry for following up off-topic

Re: [GENERAL] Caching and Blobs in PG? Was: Can PG replace redis, amqp, s3 in the future?

2017-05-04 Thread John R Pierce
On 5/4/2017 2:50 PM, John R Pierce wrote: But there's an extension - pg_cron: https://www.citusdata.com/blog/2016/09/09/pgcron-run-periodic-jobs-in-postgres/ there's also pg_agent which is a cron-like extension, usually bundled with pg_admin but also available standalone https://www.pgadm

Re: [GENERAL] Caching and Blobs in PG? Was: Can PG replace redis, amqp, s3 in the future?

2017-05-04 Thread John R Pierce
On 5/4/2017 2:08 PM, Sven R. Kunze wrote: After searching the web, it seems to me that PostgreSQL doesn't offer a cron-like background job for cleanup tasks. http://stackoverflow.com/questions/18187490/postgresql-delete-old-rows-on-a-rolling-basis But there's an extension - pg_cron: https:

Re: [GENERAL] Caching and Blobs in PG? Was: Can PG replace redis, amqp, s3 in the future?

2017-05-04 Thread John R Pierce
On 5/4/2017 2:28 PM, Alan Hodgson wrote: On Thursday 04 May 2017 14:21:00 John R Pierce wrote: or EBS, and I've heard from more than a few people that EBS can be something of a sand trap. Sorry for following up off-topic, but EBS has actually improved considerably in the last few years. You ca

Re: [GENERAL] Caching and Blobs in PG? Was: Can PG replace redis, amqp, s3 in the future?

2017-05-04 Thread Alan Hodgson
On Thursday 04 May 2017 14:21:00 John R Pierce wrote: > or EBS, and I've heard from more than a few people that EBS can be > something of a sand trap. > Sorry for following up off-topic, but EBS has actually improved considerably in the last few years. You can get guaranteed (and very high) IOPS

Re: [GENERAL] Caching and Blobs in PG? Was: Can PG replace redis, amqp, s3 in the future?

2017-05-04 Thread David G. Johnston
On Thu, May 4, 2017 at 2:08 PM, Sven R. Kunze wrote: > On 03.05.2017 12:57, Thomas Güttler wrote: > >> Am 02.05.2017 um 05:43 schrieb Jeff Janes: >> >>> ​​ >>> >>> >> No. You can certainly use PostgreSQL to store blobs. But then, you need >>> to store the PostgreSQL data **someplace**. >>> If y

Re: [GENERAL] Caching and Blobs in PG? Was: Can PG replace redis, amqp, s3 in the future?

2017-05-04 Thread John R Pierce
On 5/4/2017 2:08 PM, Sven R. Kunze wrote: No. You can certainly use PostgreSQL to store blobs. But then, you need to store the PostgreSQL data **someplace**. If you don't store it in S3, you have to store it somewhere else. I don't understand what you mean here. AFAIK storing blobs in PG is

Re: [GENERAL] Caching and Blobs in PG? Was: Can PG replace redis, amqp, s3 in the future?

2017-05-04 Thread Sven R. Kunze
On 03.05.2017 12:57, Thomas Güttler wrote: Am 02.05.2017 um 05:43 schrieb Jeff Janes: On Sun, Apr 30, 2017 at 4:37 AM, Thomas Güttler mailto:guettl...@thomas-guettler.de>> wrote: Is is possible that PostgreSQL will replace these building blocks in the future? - redis (Caching) P

[GENERAL] Caching and Blobs in PG? Was: Can PG replace redis, amqp, s3 in the future?

2017-05-03 Thread Thomas Güttler
Am 02.05.2017 um 05:43 schrieb Jeff Janes: On Sun, Apr 30, 2017 at 4:37 AM, Thomas Güttler mailto:guettl...@thomas-guettler.de>> wrote: Is is possible that PostgreSQL will replace these building blocks in the future? - redis (Caching) PostgreSQL has its own caching. It might not be