Re: [GENERAL] Postgres as key/value store

2014-09-28 Thread Thomas Kellerer
snacktime wrote on 28.09.2014 01:48: I'm looking for some feedback on the design I'm using for a basic key/value storage using postgres. Are you aware of Postgres' "native" key/value store: hstore? http://www.postgresql.org/docs/current/static/hstore.html Or Postgres JSON support? Especially

[GENERAL] call pl/pgsql function from main pl/pgsql function

2014-09-28 Thread Mehdi Ravanbakhsh
Hi All I have one main function in pl/pgsql and one subset function in pl/pgsql . i need to call Subset Function From main function and i do not need to wait for subset Function return. I just need to send parameter to subset function and do not need any thing in return. So i can call multiply

Re: [GENERAL] call pl/pgsql function from main pl/pgsql function

2014-09-28 Thread David G Johnston
Mehdi Ravanbakhsh wrote > Hi All > > I have one main function in pl/pgsql and one subset function in pl/pgsql > . > > i need to call Subset Function From main function and i do not need to > wait for subset Function return. I just need to send parameter to subset > function and do not need any

Re: [GENERAL] PANIC: could not create file "pg_xlog/xlogtemp.7884": No space left on device

2014-09-28 Thread Roopeshakumar Narayansa Shalgar (rshalgar)
Thanks Raymond. But I think the symptoms that I am seeing are different though I get the no disk space issue in the following ways: 1. There is enough disk space on my device (output of df -h), 300M is used from 56G space. /dev/mapper/data1-object--cache 58G 300M 58G

Re: [GENERAL] call pl/pgsql function from main pl/pgsql function

2014-09-28 Thread Jov
Plain pg function is synchronization,the main function must wait for the sub function over. I rember dblink can send asynchronous query,maybe you can wrap your sub function with dblink.but transition behavior should be careful thought. 2014年9月28日 8:25 PM于 "Mehdi Ravanbakhsh" 写道: > Hi All > > I hav

Re: [GENERAL] PANIC: could not create file "pg_xlog/xlogtemp.7884": No space left on device

2014-09-28 Thread Adrian Klaver
On 09/28/2014 05:52 AM, Roopeshakumar Narayansa Shalgar (rshalgar) wrote: Thanks Raymond. But I think the symptoms that I am seeing are different though I get the no disk space issue in the following ways: 1. There is enough disk space on my device (output of df -h), 300M is used from 56G spac

[GENERAL] how to see "where" SQL is better than PLPGSQL

2014-09-28 Thread Gerardo Herzig
Hi all. I see an entire database, with all the stored procedures writen in plpgsql. Off course, many (if not all) of that SP are simple inserts, updates, selects and so on. So, i want to test and show the differences between doing the same function in pgpgsql vs. plain sql. Im getting statistic

Re: [GENERAL] [SQL] how to see "where" SQL is better than PLPGSQL

2014-09-28 Thread Pavel Stehule
2014-09-28 20:30 GMT+02:00 Gerardo Herzig : > Hi all. I see an entire database, with all the stored procedures writen in > plpgsql. Off course, many (if not all) of that SP are simple inserts, > updates, selects and so on. > > So, i want to test and show the differences between doing the same > fu

Re: [GENERAL] PANIC: could not create file "pg_xlog/xlogtemp.7884": No space left on device

2014-09-28 Thread Tom Lane
Adrian Klaver writes: > On 09/28/2014 05:52 AM, Roopeshakumar Narayansa Shalgar (rshalgar) wrote: >> 4. I tried with 'archive_command = /usr/bin.true' but still I face the >> ""pg_xlog/xlogtemp.7884": No space left on device" issue. This error message is pretty specific: the OS is telling us we

Re: [GENERAL] [SQL] how to see "where" SQL is better than PLPGSQL

2014-09-28 Thread Gerardo Herzig
> Hi all. I see an entire database, with all the stored procedures > writen in plpgsql. Off course, many (if not all) of that SP are > simple inserts, updates, selects and so on. > > So, i want to test and show the differences between doing the same > function in pgpgsql vs. plain sql. > Im gettin

Re: [GENERAL] [SQL] how to see "where" SQL is better than PLPGSQL

2014-09-28 Thread Pavel Stehule
2014-09-28 21:29 GMT+02:00 Gerardo Herzig : > > Hi all. I see an entire database, with all the stored procedures > > writen in plpgsql. Off course, many (if not all) of that SP are > > simple inserts, updates, selects and so on. > > > > So, i want to test and show the differences between doing the

[GENERAL] table versioning approach (not auditing)

2014-09-28 Thread Abelard Hoffman
Hi. I need to maintain a record of all changes to certain tables so assist in viewing history and reverting changes when necessary (customer service makes an incorrect edit, etc.). I have studied these two audit trigger examples: https://wiki.postgresql.org/wiki/Audit_trigger https://wiki.postgres

Re: [GENERAL] table versioning approach (not auditing)

2014-09-28 Thread Gavin Flower
On 29/09/14 15:00, Abelard Hoffman wrote: Hi. I need to maintain a record of all changes to certain tables so assist in viewing history and reverting changes when necessary (customer service makes an incorrect edit, etc.). I have studied these two audit trigger examples: https://wiki.postgresq