Re: [GENERAL] Hardware requirements for a PostGIS server

2015-02-11 Thread Gavin Flower
On 12/02/15 12:38, Mathieu Basille wrote: [...] [1] Start of the thread here: http://lists.osgeo.org/pipermail/postgis-users/2015-February/040120.html [...] http://lists.osgeo.org/pipermail/postgis-users/2015-February/040134.html [...] * About usage being mostly read: this will be true for mos

Re: [GENERAL] Hardware requirements for a PostGIS server

2015-02-11 Thread Gavin Flower
On 12/02/15 12:38, Mathieu Basille wrote: Thanks to everyone who contributed to this thread, either on the PostGIS [1] or the PostgreSQL [2] mailing lists. I will try to summarize everything in this message, which I will actually post on both lists to give an update to everyone. I hope it can b

Re: [GENERAL] Prepared statements with bind parameters for DDL

2015-02-11 Thread Tom Lane
Martijn van Oosterhout writes: > On Wed, Feb 11, 2015 at 02:22:10PM -0500, Tom Lane wrote: >> Nope. DDL commands generally don't have any support for evaluating >> expressions, which would be the context in which parameters would >> be useful. Nor have they got plans, which would be the requirem

Re: [GENERAL] Hardware requirements for a PostGIS server

2015-02-11 Thread Mathieu Basille
Thanks to everyone who contributed to this thread, either on the PostGIS [1] or the PostgreSQL [2] mailing lists. I will try to summarize everything in this message, which I will actually post on both lists to give an update to everyone. I hope it can be useful for other people interested. Pleas

Re: [GENERAL] Prepared statements with bind parameters for DDL

2015-02-11 Thread Martijn van Oosterhout
On Wed, Feb 11, 2015 at 02:22:10PM -0500, Tom Lane wrote: > deepak writes: > > I find that one can't have a prepared statement with bind parameters for a > > DDL statement, > > Nope. DDL commands generally don't have any support for evaluating > expressions, which would be the context in which p

Re: [GENERAL] Prepared statements with bind parameters for DDL

2015-02-11 Thread Tom Lane
deepak writes: > I find that one can't have a prepared statement with bind parameters for a > DDL statement, Nope. DDL commands generally don't have any support for evaluating expressions, which would be the context in which parameters would be useful. Nor have they got plans, which would be th

Re: [GENERAL] Prepared statements with bind parameters for DDL

2015-02-11 Thread Adrian Klaver
On 02/11/2015 09:42 AM, deepak wrote: Hi, I find that one can't have a prepared statement with bind parameters for a DDL statement, although I couldn't find the rationale for this restriction. Is this limitation due to the database design, or is it something that's imposed by the SQL standard a

[GENERAL] Prepared statements with bind parameters for DDL

2015-02-11 Thread deepak
Hi, I find that one can't have a prepared statement with bind parameters for a DDL statement, although I couldn't find the rationale for this restriction. Is this limitation due to the database design, or is it something that's imposed by the SQL standard and/or the JDBC drivers? Please clarify.

Re: [GENERAL] The return of the auto-vacuum

2015-02-11 Thread Adrian Klaver
On 02/11/2015 07:49 AM, Nestor A. Diaz wrote: Hello Everybody, This is the scenario: I have a postgres 8.4, debian packages installed from pgdg repository and version equal to: 8.4.21-1.pgdg70+1 I have a GPS database that insert about 4 million records on some tables every week, the database i

[GENERAL] The return of the auto-vacuum

2015-02-11 Thread Nestor A. Diaz
Hello Everybody, This is the scenario: I have a postgres 8.4, debian packages installed from pgdg repository and version equal to: 8.4.21-1.pgdg70+1 I have a GPS database that insert about 4 million records on some tables every week, the database is partitioned per week, I do a manual vacuum eve

Re: [GENERAL] Cluster seems broken after pg_basebackup

2015-02-11 Thread Adrian Klaver
On 02/10/2015 08:38 AM, Guillaume Drolet wrote: Adrian, in response to your question: 2015-02-06 07:11:38 EST FATAL: le rôle « 208375PT$ » n'existe pas So where is role 208375PT$ supposed to come from? I found that when I stop/start/restart pgsql through the services.msc application in