From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: PostgreSQL as possible addon ?
Date: Fri, 29 Mar 2019 11:01:17 +0100 [thread overview]
Message-ID: <14efc334e76a595ba4eab654d7e38631ad1260c5.camel@ipfire.org> (raw)
In-Reply-To: <0C1A6659-9AC9-43D1-9773-9AA1D70D031E@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2870 bytes --]
Hi Michael,
haven´t seen your request...
On Mi, 2019-03-27 at 15:06 +0000, Michael Tremer wrote:
> What are your arguments for it?
Some arguments from my side:
- Since we dropped MySQL cause no one maintained it appropriately
(which was also a kind of overkill) i thought it might be nice to have
a substitute which is, in my opinion, easier to update but also some
implementations has been changed here (nothing in /srv and wider spread
in the system but now all in /var) and of course i think PostgreSQL is
also the nicer one.
- I also really like some helper tools like pgsql (also to have for
MySQL) for the not so affine SQL users but that´s only a beside one.
- Another one is, have seen some requests for a non Sqlite DB from
users in the forum where it thought i can make a try for their favorits
which was PostgreSQL clearly before MySQL.
- If someone uses IPFire also in a kind of server environment which i
do, PostgreSQL can be a nice one to have.
But again, i´ am totaly fine with your arguments and of course i can
nevertheless use it for myself.
Best,
Erik
>
> > On 27 Mar 2019, at 15:06, ummeegge <ummeegge(a)ipfire.org> wrote:
> >
> > Hi Michael,
> > OK no problem.
> >
> > Best,
> >
> > Erik
> >
> > On Mi, 2019-03-27 at 14:53 +0000, Michael Tremer wrote:
> > > Hi,
> > >
> > > I would oppose PostgreSQL as an add-on.
> > >
> > > There are two major reasons for this:
> > >
> > > * Nobody has ever requested it. At least I am not aware of it. We
> > > do
> > > not have any applications that require it or would run better if
> > > PostgreSQL was there. Since we already have loads of add-ons that
> > > are
> > > barely used and barely maintained I would like to avoid adding
> > > another.
> > >
> > > * Based on that last note, I would say that we also have enough
> > > places to do work on that constantly get stuck. Instead of
> > > opening
> > > another construction site, I would like to at least have one or
> > > more
> > > closed - or at least declare that we do not intend to work on
> > > this
> > > any more.
> > >
> > > Best,
> > > -Michael
> > >
> > > > On 27 Mar 2019, at 14:28, ummeegge <ummeegge(a)ipfire.org> wrote:
> > > >
> > > > Hi all,
> > > > another question ;-).
> > > > Since i´d build PostgreSQL for IPFire -->
> > > >
> >
> >
https://git.ipfire.org/?p=people/ummeegge/ipfire-2.x.git;a=commit;h=230d0569d3f24b608852328a983b1791731aee4c
> > > > <-- only testing version
> > > > and made also some testings with it -->
> > > > https://forum.ipfire.org/viewtopic.php?f=50&t=22476
> > > > incl. pgcli --> https://www.pgcli.com/ i wanted to ask if it
> > > > would
> > > > make
> > > > sense to deliver it to the mailinglist ?
> > > >
> > > > Best,
> > > >
> > > > Erik
> > > >
> > > >
> > >
> > >
>
>
next prev parent reply other threads:[~2019-03-29 10:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 14:28 ummeegge
2019-03-27 14:53 ` Michael Tremer
2019-03-27 15:06 ` ummeegge
2019-03-27 15:06 ` Michael Tremer
2019-03-29 10:01 ` ummeegge [this message]
2019-03-29 14:11 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=14efc334e76a595ba4eab654d7e38631ad1260c5.camel@ipfire.org \
--to=ummeegge@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox