Re: [GENERAL] Why does this hot standy archive_command work

> On Jan 20, 2017, at 7:03 PM, bto...@computer.org > wrote: > > While learning a bit about basic hot standby configuration, I was reviewing > an article that used these parameters > > wal_level = 'hot_standby' > archive_mode = on > archive_command = 'cd .' >

[GENERAL] Why does this hot standy archive_command work

While learning a bit about basic hot standby configuration, I was reviewing an article that used these parameters wal_level = 'hot_standby' archive_mode = on archive_command = 'cd .' max_wal_senders = 1 hot_standby = on How or why that particular archive_command actually works (... and it does

[GENERAL] Can we not give tyrannical pedants control of #postgresql?

Hi all! It's really a bad sign when some user is given operator status who is intolerant to minor offtopic conversations that span no more than a couple of line buffers. Witnessing a user getting kicked for asking for my location was way beyond reasonable, considering even the channel was

Re: [GENERAL] update error with serializable

On Fri, Jan 20, 2017 at 11:27 AM, Rob Sargent wrote: > On 01/20/2017 10:05 AM, Kevin Grittner wrote: >> https://www.postgresql.org/message-id/flat/d8joa0eh9yw@dalvik.ping.uio.no#d8joa0eh9yw@dalvik.ping.uio.no > Configurable or dynamic? Wouldn't something related

Re: [GENERAL] update error with serializable

On 01/20/2017 10:05 AM, Kevin Grittner wrote: On Fri, Jan 20, 2017 at 4:44 AM, Tom DalPozzo wrote: I've two threads countinuously updataing rows in the same table. Each one does: BEGIN, UPDATE,UPDATECOMMIT There can't be two active transactions updating the same

Re: [GENERAL] update error with serializable

On Fri, Jan 20, 2017 at 4:44 AM, Tom DalPozzo wrote: > I've two threads countinuously updataing rows in the same table. > Each one does: BEGIN, UPDATE,UPDATECOMMIT > There can't be two active transactions updating the same row (my > bug apart but I don't think so). >

Re: [GENERAL] migrate Sql Server database to PostgreSql

-- David Rader dav...@openscg.com On Thu, Jan 19, 2017 at 8:56 AM, Kenneth Marshall wrote: > On Thu, Jan 19, 2017 at 03:29:34PM +1100, Venkata B Nagothi wrote: > > On Thu, Jan 19, 2017 at 6:17 AM, PAWAN SHARMA > > > wrote: > > > > > Hello All, > > > >

Re: [GENERAL] view dependent on system view caused an upgrade to fail

"Hu, Patricia" writes: > I have the following function and view in my db: > create or replace function ${catalogSchema}.fn_show_pg_stat_activity() > returns setof pg_catalog.pg_stat_activity as $$ select * from > pg_catalog.pg_stat_activity; $$ language sql volatile

[GENERAL] view dependent on system view caused an upgrade to fail

I have the following function and view in my db: create or replace function ${catalogSchema}.fn_show_pg_stat_activity() returns setof pg_catalog.pg_stat_activity as $$ select * from pg_catalog.pg_stat_activity; $$ language sql volatile security definer; create or replace view

Re: [GENERAL] Start/stop postgresql with pg_ctl or service without root access on RHEL

Jean-Michel Scheiwiler writes: > We plan to use postgresql on RHEL 6. > DBAs won't have root access but they will need to start/stop the databases. > They'll be able to do so with pg_ctl as postgres. > However databases should also start automatically when the server

[GENERAL] Start/stop postgresql with pg_ctl or service without root access on RHEL

Hello We plan to use postgresql on RHEL 6. DBAs won't have root access but they will need to start/stop the databases. They'll be able to do so with pg_ctl as postgres. However databases should also start automatically when the server reboots and so we should use services

[GENERAL] update error with serializable

Hi, I've two threads countinuously updataing rows in the same table. Each one does: BEGIN, UPDATE,UPDATECOMMIT There can't be two active transactions updating the same row (my bug apart but I don't think so). I'm using default_transaction_isolation = 'serializable' I get "could not serialize