Hi all,
I am working on a postgresql performance tuning tool for my project.
Having done a lot of research and googling for manual and autovacuum
parameters ,I have met a dead end. Could you tell me what are the
recommended value for all the manual and autovacuum parameters.
I am looking for a
On Sat, Feb 1, 2014 at 9:20 AM, prashant Pandey
wrote:
> I am looking for actual value. And please if you mention the database
> condition along with the recommendation ,it will be helpfull.
Maybe the question has to be reversed: what is the condition you are
aiming at optimizing?
Luca
--
Sen
I do:
SELECT '{{1,2},{3,4}}'::INTEGER[][]
But I get:
{{1,2},{3,4}} INTEGER[]. Somehow the PostgreSQL server does not understand
that is a multidimensional array. So, later if I want to get {1,2} or {3,4},
the field[1] or field[2]. Evem when I try:
field [1:1] I get {{1,2}} and not plain one dim
On Sat, Feb 1, 2014 at 1:34 PM, Anh Pham wrote:
> Hi,
> I actually included 'postgres.h'
>
> However I found out that when I stopped the server, the code then compiled
> successfully.
Code compilation and a server status are not related as compilation of
Postgres-related modules require the librar
On Sat, Feb 1, 2014 at 6:45 PM, alexandros_e wrote:
> I do:
>
> SELECT '{{1,2},{3,4}}'::INTEGER[][]
>
> But I get:
>
> {{1,2},{3,4}} INTEGER[]. Somehow the PostgreSQL server does not understand
> that is a multidimensional array. So, later if I want to get {1,2} or {3,4},
> the field[1] or field[2
Thankyou for your reply. I just want to know that what are the strting
recommended value for the vacuum parameters. As in what values are
unacceptable and cause problems to our database and which values will work
for a normal database
Regards.
On 1 Feb 2014 15:15, "Luca Ferrari" wrote:
> On Sat,
This is probably the only way to do it. Still, it seems to me an overkill if
basically you need to run a function at each multidimensional array to get
access to each i-array element. Thanks for your answer.
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Postgresql-mu
On Sat, Feb 1, 2014 at 2:16 PM, prashant Pandey
wrote:
> Thankyou for your reply. I just want to know that what are the strting
> recommended value for the vacuum parameters.
The defaults values. Or at least, I will trust such values as good
starting values.
> As in what values are
> unacceptabl
I have a postgresql dB where I want to SNMP some information from a few
servers and store them in my database. Is this something that can be done
with a stored procedure or do I have to build an external utility type of
app? If it is doable is this something the postgeres language or do I have
to d
On 02/01/2014 12:59 PM, bobspero wrote:
I have a postgresql dB where I want to SNMP some information from a few
servers and store them in my database. Is this something that can be done
with a stored procedure or do I have to build an external utility type of
app? If it is doable is this somethin
It is possible to put a PostgreSQL database in substitution of a Oracle
database for an app running BDE?
Any tips (beyond obvious "check Oracle specific funcionality")?
Regards,
Edson
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
h
On 2/1/2014 3:18 PM, Edson Richter wrote:
It is possible to put a PostgreSQL database in substitution of a
Oracle database for an app running BDE?
Any tips (beyond obvious "check Oracle specific funcionality")?
what is BDE ?
--
john r pierce 37N 122W
som
Hi,
Is there any technical reason why wal_writer_delay is limited to 10s?
I am using postgresql in an embedded system and writing every 10s
burns flash at an amazing rate (a 32GB SDHC card with ext4 survived 4 days with
only a few GB written).
I've now switched to nilfs2 which is way more friendl
On Sat, Feb 1, 2014 at 3:40 PM, Clemens Eisserer wrote:
> Something like wal_writer_delay=600s would be ideal, I can afford to
> loose a 10min of data, but can't afford to get a corrupted database
> after power loss.
What Postgres version? The WAL Writer will hibernate on Postgres 9.2+.
walwriter
On Sat, Feb 1, 2014 at 3:48 PM, Peter Geoghegan
wrote:
> What Postgres version? The WAL Writer will hibernate on Postgres 9.2+.
Of course, it will still write things out at a steady rate if they're
there to write. However, there is no reason to think you couldn't
change things in guc.c to have th
On 02/01/2014 03:26 PM, John R Pierce wrote:
On 2/1/2014 3:18 PM, Edson Richter wrote:
It is possible to put a PostgreSQL database in substitution of a
Oracle database for an app running BDE?
Any tips (beyond obvious "check Oracle specific funcionality")?
what is BDE ?
http://en.wikipedia.o
On 2/1/2014 4:26 PM, Adrian Klaver wrote:
On 02/01/2014 03:26 PM, John R Pierce wrote:
On 2/1/2014 3:18 PM, Edson Richter wrote:
It is possible to put a PostgreSQL database in substitution of a
Oracle database for an app running BDE?
Any tips (beyond obvious "check Oracle specific funcionality"
Hi Peter,
Thanks a lot for your reply.
> What Postgres version? The WAL Writer will hibernate on Postgres 9.2+.
> walwriter.c says:
I am using Postgresql-9.1 shipped with Raspbian (debian for raspberry pi).
> /*
> * Number of do-nothing loops before lengthening the delay time, and the
> * mul
On Sat, Feb 1, 2014 at 10:49 PM, Clemens Eisserer wrote:
> My question on the list was merely to make sure there are no
> side-effects when increasing this delay above what seems to be
> considered safe limits. However, I still wonder why this parameter is
> capped to 10s and whether this restrict
19 matches
Mail list logo
