In term of performance and reliability the differences are minor.
The main difference is that for PostgreSQL, the DB process will run outside
the JVM of Artifactory. So, if you have a 32bit JVM you get OutOfMemory
faster with DerbyDB (Web Server + Artifactory + DB Engine) than with
PostgreSQL.
The other difference is dump restore procedures can be done directly on the
PostgreSQL engine without having the Artifactory JVM up and running. That
usually simplify the operation processes.
Hope I was clear :)
Fred.
On Fri, Apr 16, 2010 at 9:25 PM, shawn_ayers <[email protected]> wrote:
>
> Would there be any advantage to using PostgreSQL over the standard Derby
> that
> comes bundled with Artifactory?
>
>
> freddy33 wrote:
> >
> > Hi Shawn,
> >
> > For files of this size, I highly suggest you use a filesystem datastore.
> > It
> > will be faster and it will work with PostgreSQL :)
> > Just take the /etc/filesystem-mysql/repo.xml file and change the DB
> > setups.
> >
> > Hope it helps,
> > Fred.
> >
> > On Fri, Apr 16, 2010 at 9:16 PM, shawn_ayers <[email protected]>
> > wrote:
> >
> >>
> >> I know believe that the Bind message length error is related to the
> >> PostgreSQL database blob size limitation of 1 GB. I have successfully
> >> uploaded the same file to another Artifactory server running the
> standard
> >> Derby database configuration.
> >>
> >>
> >>
> >> shawn_ayers wrote:
> >> >
> >> > I believe I was hitting a browser size limitation. I reduced the file
> >> > size below the 2 GB maximum and it did upload, but when deploying into
> >> > Artifactory with PostgreSQL I encountered the following error:
> >> >
> >> > Cannot deploy file GB_TEST_FILE.zip. Cause: Bind message length
> >> > 1,469,053,112 too long. This can be caused by very large or incorrect
> >> > length specifications on InputStream parameters.
> >> >
> >> > Would this be caused by PostgreSQL's field limitation of 1 GB maximum?
> >> >
> >> > Thank you,
> >> >
> >> > Shawn
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > shawn_ayers wrote:
> >> >>
> >> >> I suppose I could be hitting a browser file upload limit.
> >> >>
> >> >>
> >> >> shawn_ayers wrote:
> >> >>>
> >> >>> I am running into an issue uploading, from a browser, a 4.5 GB .ISO
> >> >>> file into Artifactory and each time I am running into the same
> issue:
> >> >>>
> >> >>> * The browser either errors out and goes to a blank page or in
> Google
> >> >>> Chrome I receive the following:
> >> >>>
> >> >>> "Upload Failed: Request was rejected because its size is unknown"
> >> >>>
> >> >>> I have attempted to upload this file into the following
> >> configurations,
> >> >>> with the same result:
> >> >>>
> >> >>> 1.) Artifactoy connected to a PostgreSQL database
> >> >>>
> >> >>> and
> >> >>>
> >> >>> 2.) Artifactory out of the box fronting the filesystem as the
> storage
> >> >>> repository.
> >> >>>
> >> >>> I have already changed the "File Upload Max Size" to 0
> >> >>>
> >> >>> I am running Artifactory Ver 2.2.2 (rev. 10427)
> >> >>>
> >> >>> I suppose I could be running into a size limit based upon the
> >> browser.
> >> >>>
> >> >>> Thank you,
> >> >>>
> >> >>> Shawn
> >> >>>
> >> >>
> >> >>
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >>
> http://old.nabble.com/Large-File-Upload-Causing-Error-tp28269635p28270231.html
> >> Sent from the Artifactory-Users mailing list archive at Nabble.com.
> >>
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> Download Intel® Parallel Studio Eval
> >> Try the new software tools for yourself. Speed compiling, find bugs
> >> proactively, and fine-tune applications for parallel performance.
> >> See why Intel Parallel Studio got high marks during beta.
> >> http://p.sf.net/sfu/intel-sw-dev
> >> _______________________________________________
> >> Artifactory-users mailing list
> >> [email protected]
> >> https://lists.sourceforge.net/lists/listinfo/artifactory-users
> >>
> >
> >
> >
> > --
> > Co. Founder and Chief Architect
> > JFrog Ltd
> > http://www.jfrog.org/
> > http://twitter.com/freddy33
> >
> >
> ------------------------------------------------------------------------------
> > Download Intel® Parallel Studio Eval
> > Try the new software tools for yourself. Speed compiling, find bugs
> > proactively, and fine-tune applications for parallel performance.
> > See why Intel Parallel Studio got high marks during beta.
> > http://p.sf.net/sfu/intel-sw-dev
> > _______________________________________________
> > Artifactory-users mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/artifactory-users
> >
> >
>
> --
> View this message in context:
> http://old.nabble.com/Large-File-Upload-Causing-Error-tp28269635p28270328.html
> Sent from the Artifactory-Users mailing list archive at Nabble.com.
>
>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Artifactory-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>
--
Co. Founder and Chief Architect
JFrog Ltd
http://www.jfrog.org/
http://twitter.com/freddy33
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
