Re: Possible bug: SQL function parameter in window frame definition

> "Tom" == Tom Lane writes: >> Here is a draft patch along those lines; the intent of this one is >> that no existing walker or mutator should need to change (the change >> to the dependency code is basically cosmetic I believe, just avoids >> walking some things twice). Tom> Hmm. I th

Re: Redis 16 times faster than Postgres?

On Sep 29, 2019, at 8:44 PM, Ron wrote: > > On 9/29/19 8:09 PM, Steve Litt wrote: >> On Mon, 30 Sep 2019 07:46:14 +1000 >> Nathan Woodrow wrote: >> >>> Redis is a in memory database so I would except it to be always much >>> faster.. >> Is there a way to have Redis periodically update an on-dis

Re: Redis 16 times faster than Postgres?

On Sun, Sep 29, 2019 at 04:52:15PM -0500, Ron wrote: > On 9/29/19 4:42 PM, Colin 't Hart wrote: > Redis is an in-memory key-value database. PostgreSQL... isn't. Well, I think that you have never heard about the urban legend of running Postgres on scissors then and this reminds me of this blog post

Re: Redis 16 times faster than Postgres?

On 9/29/19 8:09 PM, Steve Litt wrote: On Mon, 30 Sep 2019 07:46:14 +1000 Nathan Woodrow wrote: Redis is a in memory database so I would except it to be always much faster.. Is there a way to have Redis periodically update an on-disk backup? That would be great, but otherwise you're at the mer

Re: Redis 16 times faster than Postgres?

Steve Litt wrote: > On Mon, 30 Sep 2019 07:46:14 +1000 > Nathan Woodrow wrote: > > > Redis is a in memory database so I would except it to be always much > > faster.. > > Is there a way to have Redis periodically update an on-disk backup? > That would be great, but otherwise you're at the mercy

Re: Redis 16 times faster than Postgres?

On Mon, 30 Sep 2019 07:46:14 +1000 Nathan Woodrow wrote: > Redis is a in memory database so I would except it to be always much > faster.. Is there a way to have Redis periodically update an on-disk backup? That would be great, but otherwise you're at the mercy of your power company (here in Cen

Re: Redis 16 times faster than Postgres?

> Back-end web servers don't have human nervous systems. Faster response time means that a give bit of hardware can support > a much higher load, saving you money Fair point, I can't argue against it as stated. Although I have no way of know if this person's site is *ever* overloaded or has any c

Re: Redis 16 times faster than Postgres?

On 9/29/19 7:01 PM, Morris de Oryx wrote: Sigh. I despair of "16x faster" and "20x faster" headlines that ignore the raw numbers. *The worst numbers in there are far below the threshold of user perception*. Unless these results are compounded by running in a loop, they are meaningless. Not imme

Re: Redis 16 times faster than Postgres?

Sigh. I despair of "16x faster" and "20x faster" headlines that ignore the raw numbers. *The worst numbers in there are far below the threshold of user perception*. Unless these results are compounded by running in a loop, they are meaningless. Not immeasurable, just meaningless. https://www.nngro

Re: Redis 16 times faster than Postgres?

On 9/29/19 4:42 PM, Colin 't Hart wrote: Hi, Can someone take a look at this blog post? https://www.peterbe.com/plog/redis-vs-postgres-blob-of-json Can Redis really be 16 times faster than Postgres? Surely Postgres can get closer to the raw speed of the hardware than 1 order of magnitude? Re

Re: Redis 16 times faster than Postgres?

Redis is a in memory database so I would except it to be always much faster.. On Mon., 30 Sep. 2019, 7:42 am Colin 't Hart, wrote: > Hi, > > Can someone take a look at this blog post? > https://www.peterbe.com/plog/redis-vs-postgres-blob-of-json > > Can Redis really be 16 times faster than Postg

Redis 16 times faster than Postgres?

Hi, Can someone take a look at this blog post? https://www.peterbe.com/plog/redis-vs-postgres-blob-of-json Can Redis really be 16 times faster than Postgres? Surely Postgres can get closer to the raw speed of the hardware than 1 order of magnitude? Thanks, Colin

Re: Thoughts on a cosntraint ?

On 9/29/19 12:40 PM, stan wrote: I have a table that consists of 3 columns. vendor_key mfg_key preferred (boolean) The idea is that a given vendor is the vendor we want to use for each manufacturer for a given project. I need to constrain such that only on row of mfg, vendor and project can b

Re: Thoughts on a cosntraint ?

> On Sep 29, 2019, at 1:52 PM, John W Higgins wrote: > > On Sun, Sep 29, 2019 at 12:40 PM stan > wrote: > I have a table that consists of 3 columns. > > vendor_key > mfg_key > preferred (boolean) > > The idea is that a given vendor is the vendor we want to use for eac

Re: Thoughts on a cosntraint ?

On Sun, Sep 29, 2019 at 12:40 PM stan wrote: > I have a table that consists of 3 columns. > > vendor_key > mfg_key > preferred (boolean) > > The idea is that a given vendor is the vendor we want to use for each > manufacturer for a given project. > > I need to constrain such that only on row of

Thoughts on a cosntraint ?

I have a table that consists of 3 columns. vendor_key mfg_key preferred (boolean) The idea is that a given vendor is the vendor we want to use for each manufacturer for a given project. I need to constrain such that only on row of mfg, vendor and project can be set to TRUE. I would be interest

Re: Possible bug: SQL function parameter in window frame definition

Andrew Gierth writes: > "Andrew" == Andrew Gierth writes: > Andrew> We could minimize the chance of breakage in a back-patched fix > Andrew> by having query_tree_walker/mutator iterate the windowClause > Andrew> list itself > Here is a draft patch along those lines; the intent of this one is

Re: Possible bug: SQL function parameter in window frame definition

> "Andrew" == Andrew Gierth writes: Andrew> We could minimize the chance of breakage in a back-patched fix Andrew> by having query_tree_walker/mutator iterate the windowClause Andrew> list itself Here is a draft patch along those lines; the intent of this one is that no existing walker or

Re: How to handle things that change over time?

On 13/09/2019 17:19, Paul Jungwirth wrote: > The SQL:2011 standard also has temporal primary keys, foreign keys, > SELECTs, and UPDATE/DELETEs, and we're working on adding those too. And here is a full implementation of all that: https://github.com/xocolatl/periods/ It is packaged in both the deb