Re: [GENERAL] postgres 9.3

You are correct John, but in this case, he stated only one (1) database. So changing the search path in .postgresql.conf simplifies things for all users. However, should he create additional databases later on, then yes, your solution would be better. On Mon, Sep 21, 2015 at 3:08 PM, Alvaro Herre

Re: [GENERAL] postgres 9.3

John R Pierce wrote: > better would be to... > > ALTER ROLE username SET SEARCH_PATH='preview,"$user", public'; > or > ALTER DATABASE dbname SET...; > > and then this change just applies to that named role or database... (or ALTER ROLE username IN DATABASE dbname SET .. which applies

Re: [GENERAL] postgres 9.3

On 9/21/2015 11:52 AM, Melvin Davidson wrote: You cannot directly "connect" one schema with another, but you can set the default to have both in the search_path. Uncomment the #search_path parameter in Postgresql.conf and change it to search_path = 'preview, role,public,"$user",public' the abo

Re: [GENERAL] postgres 9.3

You cannot directly "connect" one schema with another, but you can set the default to have both in the search_path. Uncomment the #search_path parameter in Postgresql.conf and change it to search_path = 'preview, role,public,"$user",public' The make sure you do: sudo su - postgres pg_ctl reload [-

[GENERAL] postgres 9.3

I have one database and two schemas in that public,preview and role preview automatically i want to connect preview schema with preview role. set search_path to preview. show search_path; .. preview. when disconnect and connect database it's showing $user$:public schema not showing preview. wha

Re: [GENERAL] postgres 9.3

On 8/1/2015 3:08 AM, Andreas Joseph Krogh wrote: The version goes last: service postgresql start 9.3 thats very OS/distribution specific. -- john r pierce, recycling bits in santa cruz

Re: [GENERAL] postgres 9.3

På fredag 31. juli 2015 kl. 18:39:24, skrev Ramesh T < rameshparnandit...@gmail.com >: I changed archive_command in postgresql.conf and restarted it.postgres 3 installed on linux.connected from putty.after restarted it getting message like     -bash-4.1$ servic

Re: [GENERAL] postgres 9.3

On 7/31/2015 9:39 AM, Ramesh T wrote: -bash-4.1$ service postgres-9.3 start postgres-9.3: unrecognized service on redhat/centos type systems, the service name is postgresql-9.3 note that the service command is meant to be run by the root user, a $ prompt in bash generally indicates you're not

Re: [GENERAL] postgres 9.3

On 07/31/2015 09:39 AM, Ramesh T wrote: I changed archive_command in postgresql.conf and restarted it.postgres 3 installed on linux.connected from putty. There is no Postgres 3, but given your comments below I going to go on the assumption you are talking about 9.3. What Linux distribution a

[GENERAL] postgres 9.3

I changed archive_command in postgresql.conf and restarted it.postgres 3 installed on linux.connected from putty. after restarted it getting message like -bash-4.1$ service postgres-9.3 start postgres-9.3: unrecognized service but files available at server side.. any help..?

Re: [GENERAL] Postgres 9.3 tuning advice

Hello, On Wed, Aug 13, 2014 at 5:28 PM, Marti Raudsepp wrote: > On Wed, Aug 13, 2014 at 9:44 AM, Albe Laurenz > wrote: > > Set wal_buffers to 16MB so that a whole WAL segment will fit. > > No need, wal_buffers is automatically tuned now. If your > shared_buffers is 512MB or larger, wal_buffers

Re: [GENERAL] Postgres 9.3 tuning advice

On Wed, Aug 13, 2014 at 9:44 AM, Albe Laurenz wrote: > Set wal_buffers to 16MB so that a whole WAL segment will fit. No need, wal_buffers is automatically tuned now. If your shared_buffers is 512MB or larger, wal_buffers will be 16MB. Regards, Marti -- Sent via pgsql-general mailing list (pgs

Re: [GENERAL] Postgres 9.3 tuning advice

dushy wrote: > Iam running a postgresql 9.0.13 master/slave instance in a write heavy > workload. > > The hardware is a Dell 720, E5530 - 8 core, 128GB RAM. The database (around > 250g with indexes/bloat etc) is sitting on flashcache device with 2 fusion- > io PCIe MLC SSDs as frontend and a MD320

[GENERAL] Postgres 9.3 tuning advice

Hello all, Iam running a postgresql 9.0.13 master/slave instance in a write heavy workload. The hardware is a Dell 720, E5530 - 8 core, 128GB RAM. The database (around 250g with indexes/bloat etc) is sitting on flashcache device with 2 fusion- io PCIe MLC SSDs as frontend and a MD3200 based RA

Re: [GENERAL] Postgres 9.3 Installation Problems Windows 7 64 Bit Pro

Uninstall postgres. Reset windows socket. Go to command prompt ---> */netsh winsock reset/* Now you should be able to install the postgres succesfully. Good Luck!! -- View this message in context: http://postgresql.1045698.n5.nabble.com/Postgres-9-3-Installation-Problems-Windows-7-64-Bit-Pro-t

Re: [GENERAL] Postgres 9.3 read block error went into recovery mode

Thanks everyone for the reply. So I would conclude it as OpenVZ problem, probably we will run some further check just to make sure no data corruption. Many thanks again :) On Thu, Dec 5, 2013 at 12:23 AM, Kevin Grittner wrote: > Albe Laurenz wrote: > > Shuwn Yuan Tee wrote: > > > >> We recent

Re: [GENERAL] Postgres 9.3 read block error went into recovery mode

On Tue, Dec 3, 2013 at 4:32 AM, Shuwn Yuan Tee wrote: > We recently experienced crash on out postgres production server. Here's our > server environment: > > - Postgres 9.3 > - in OpenVZ container > - total memory: 64GB > > > Here's the error snippet from postgres log: > > ERROR: could not read b

Re: [GENERAL] Postgres 9.3 read block error went into recovery mode

Albe Laurenz wrote: > Shuwn Yuan Tee wrote: > >> We recently experienced crash on out postgres production server. >> Here's our server environment: >> - in OpenVZ container >> ERROR:  could not read block 356121 in file "base/33134/33598.2": Bad address >> >> LOG:  server process (PID 21119) was

Re: [GENERAL] Postgres 9.3 read block error went into recovery mode

Shuwn Yuan Tee wrote: > We recently experienced crash on out postgres production server. Here's our > server environment: > > - Postgres 9.3 > - in OpenVZ container > - total memory: 64GB > > > Here's the error snippet from postgres log: > > ERROR: could not read block 356121 in file "base/33

[GENERAL] Postgres 9.3 read block error went into recovery mode

We recently experienced crash on out postgres production server. Here's our server environment: - Postgres 9.3 - in OpenVZ container - total memory: 64GB Here's the error snippet from postgres log: ERROR: could not read block 356121 in file "base/33134/33598.2": Bad address LOG: server proces

Re: [GENERAL] Postgres 9.3 Installation Problems Windows 7 64 Bit Pro

It should be possible to install the SW without initializing the cluster. That way you may be in a better position to troubleshoot the issue. Complete the installation, then use initdb to initialize a cluster. Have a look at this url too - http://wiki.postgresql.org/wiki/Running_%26_Installing_Post

[GENERAL] Postgres 9.3 Installation Problems Windows 7 64 Bit Pro

Hi, We are having a problem installing Postgres 9.3 on Windows 7 pro. The installation freezes and you can leave it running overnight without any error messages. The Bitrock log's last entries are: [14:45:43] Removing the existing ldconfig setting - set during the previous instal

Re: [GENERAL] Postgres 9.3 beta log

On Sat, Aug 10, 2013 at 09:52:48PM +0200, Stefan Kaltenbrunner wrote: > On 08/10/2013 04:21 PM, Bruce Momjian wrote: > > On Sat, Aug 10, 2013 at 06:38:57AM +, Arvind Singh wrote: > >> as you can see it is for a single record "login88193" it places > >> > >> PARSER STATISTICS > >> PARSE ANALYSIS

Re: [GENERAL] Postgres 9.3 beta log

On 08/10/2013 04:21 PM, Bruce Momjian wrote: > On Sat, Aug 10, 2013 at 06:38:57AM +, Arvind Singh wrote: >> as you can see it is for a single record "login88193" it places >> >> PARSER STATISTICS >> PARSE ANALYSIS STATISTICS >> REWRITER STATISTICS >> >> I know it appers because i have enabled l

Re: [GENERAL] Postgres 9.3 beta log

On Sat, Aug 10, 2013 at 06:38:57AM +, Arvind Singh wrote: > as you can see it is for a single record "login88193" it places > > PARSER STATISTICS > PARSE ANALYSIS STATISTICS > REWRITER STATISTICS > > I know it appers because i have enabled log_parser_* options in log > > But what i request t

[GENERAL] Postgres 9.3 beta log

Hello and namaste, I have installed the latest version an running tests on it. Since i analyze logs , i have found three new entries in log for each insert statement which isn't present in postgres 9.0 log --- 2013-08-10 11:59:27.031 IST,"postgres","aeppos",2780,"192.168.10.19:50935",5205dd5b.