| Lists: | pgsql-www |
|---|
| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | pgsql-www <pgsql-www(at)postgresql(dot)org> |
| Subject: | Split security info into current/historic |
| Date: | 2015-01-28 18:20:30 |
| Message-ID: | 54C9286E.2090702@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-www |
Folks,
I tried to split support/security into current and historic pages (the
later covering expired versions of postgres) ages ago and my patch was
rejected. I can't find that now, and IIRC it was pre-Django anyway.
Can someone remind me of what the restrictions around this were, if any?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | pgsql-www <pgsql-www(at)postgresql(dot)org> |
| Subject: | Re: Split security info into current/historic |
| Date: | 2015-01-28 18:44:31 |
| Message-ID: | CABUevExSiXEKOqYDY5pe7Q-6jmyg0r4hT_M0d5arYpxA57Auew@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-www |
On Wed, Jan 28, 2015 at 7:20 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> Folks,
>
> I tried to split support/security into current and historic pages (the
> later covering expired versions of postgres) ages ago and my patch was
> rejected. I can't find that now, and IIRC it was pre-Django anyway.
> Can someone remind me of what the restrictions around this were, if any?
>
One of the things on the TODO list is to move that data into the db and
generate the page, to make it easier update and less error-prone. IIRC,
last time we talked about the split, we said we should do the db thing
first, and then it could easily auto-split on "affects supported version".
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | pgsql-www <pgsql-www(at)postgresql(dot)org> |
| Subject: | Re: Split security info into current/historic |
| Date: | 2015-01-28 19:39:00 |
| Message-ID: | 54C93AD4.2040307@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | Postg토토 사이트 순위SQL : Postg토토 사이트 순위SQL 메일 링리스트 : 2015-01-28 이후 PGSQL www 19:39 |
On 01/28/2015 10:44 AM, Magnus Hagander wrote:
>
> On Wed, Jan 28, 2015 at 7:20 PM, Josh Berkus <josh(at)agliodbs(dot)com
> <mailto:josh(at)agliodbs(dot)com>> wrote:
>
> Folks,
>
> I tried to split support/security into current and historic pages (the
> later covering expired versions of postgres) ages ago and my patch was
> rejected. I can't find that now, and IIRC it was pre-Django anyway.
> Can someone remind me of what the restrictions around this were, if any?
>
>
> One of the things on the TODO list is to move that data into the db and
> generate the page, to make it easier update and less error-prone. IIRC,
> last time we talked about the split, we said we should do the db thing
> first, and then it could easily auto-split on "affects supported version".
Is the DB move really going to happen soon enough that it doesn't make
sense to split the page now?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | pgsql-www <pgsql-www(at)postgresql(dot)org> |
| Subject: | Re: Split security info into current/historic |
| Date: | 2015-02-02 14:37:44 |
| Message-ID: | CABUevEzrZZ4VUQYp0Et1HypMax=2bjLuBU+2hzi_ZGu2JO06cQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-www |
On Wed, Jan 28, 2015 at 8:39 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> On 01/28/2015 10:44 AM, Magnus Hagander wrote:
> >
> > On Wed, Jan 28, 2015 at 7:20 PM, Josh Berkus <josh(at)agliodbs(dot)com
> > <mailto:josh(at)agliodbs(dot)com>> wrote:
> >
> > Folks,
> >
> > I tried to split support/security into current and historic pages
> (the
> > later covering expired versions of postgres) ages ago and my patch
> was
> > rejected. I can't find that now, and IIRC it was pre-Django anyway.
> > Can someone remind me of what the restrictions around this were, if
> any?
> >
> >
> > One of the things on the TODO list is to move that data into the db and
> > generate the page, to make it easier update and less error-prone. IIRC,
> > last time we talked about the split, we said we should do the db thing
> > first, and then it could easily auto-split on "affects supported
> version".
>
> Is the DB move really going to happen soon enough that it doesn't make
> sense to split the page now?
>
>
Well, splitting that page in any useful form source based is probably quite
a bit of work. If that work is spent on db'ifying it, I think it's almost
done already? :P
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | pgsql-www <pgsql-www(at)postgresql(dot)org> |
| Subject: | Re: Split security info into current/historic |
| Date: | 2015-02-03 06:31:51 |
| Message-ID: | 54D06B57.1080305@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-www |
> Well, splitting that page in any useful form source based is probably
> quite a bit of work. If that work is spent on db'ifying it, I think it's
> almost done already? :P
Splitting the static page? I think it would take me less time to do it
than to discuss it.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | pgsql-www <pgsql-www(at)postgresql(dot)org> |
| Subject: | Re: Split security info into current/historic |
| Date: | 2015-02-03 14:54:44 |
| Message-ID: | CABUevEy3VM4isC7YC7-zHsxiDPu_7nZcXKpn5t=2TM_VPn2mqA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | 503 토토 페치 실패 |
On Tue, Feb 3, 2015 at 7:31 AM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>
> > Well, splitting that page in any useful form source based is probably
> > quite a bit of work. If that work is spent on db'ifying it, I think it's
> > almost done already? :P
>
> Splitting the static page? I think it would take me less time to do it
> than to discuss it.
>
>
And my argument is that DBifying it would probably not be much more than
that. Actually, the biggst time-sink of DBifying it is probably importing
the old data..
Anyway, if it's that easy, just do it.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | pgsql-www <pgsql-www(at)postgresql(dot)org> |
| Subject: | Re: Split security info into current/historic |
| Date: | 2015-02-03 19:22:45 |
| Message-ID: | 54D12005.6010005@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | Postg젠 토토SQL : Postg젠 토토SQL 메일 링리스트 : 2015-02-03 이후 PGSQL WWW 19:22 |
On 02/03/2015 06:54 AM, Magnus Hagander wrote:
> On Tue, Feb 3, 2015 at 7:31 AM, Josh Berkus <josh(at)agliodbs(dot)com
> <mailto:josh(at)agliodbs(dot)com>> wrote:
>
>
> > Well, splitting that page in any useful form source based is probably
> > quite a bit of work. If that work is spent on db'ifying it, I think it's
> > almost done already? :P
>
> Splitting the static page? I think it would take me less time to do it
> than to discuss it.
>
>
> And my argument is that DBifying it would probably not be much more than
> that. Actually, the biggst time-sink of DBifying it is probably
> importing the old data..
>
> Anyway, if it's that easy, just do it.
After the next release, now.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com