Hi,
Am 03.11.2017 um 12:51 schrieb Neto pr:
But I'm not finding where the postgresql.conf file is.
you can ask the database, inside psql:
test=# show config_file;
config_file
-
/etc/postgresql/10/main/postgresql.conf
(1 Zeile)
Hi,
You can find the file locations on
https://wiki.debian.org/PostgreSql#File_locations
You should find the configuration in /etc/postgresql/9.6/main.
Kind regards,
On 11/03/2017 12:51 PM, Neto pr wrote:
>
> Hello All
>
> I was trying to install postgresql by this tutorial
>
Hello All
I was trying to install postgresql by this tutorial
http://powa.readthedocs.io/en/latest/quickstart.html to use the tool for bd
Powa.
I am use S.O. debian 8 Jessie.
I ran: apt-get install postgresql-9.6 postgresql-client-9.6
postgresql-contrib-9.6 apt-get install postgresql-9.6-powa
Hi,
FYI, the RH rpm contains the following comment in postgresql.conf,
which is not in the postgresql.org rpm. I found it helpful.
@@ -61,11 +61,7 @@
# defaults to 'localhost'; use
'*' for all # (change requires restart)
#port = 5432
I agree with Adrian. If this is on a Linux system, I'd suggest setting up
"icrond" to monitor that file and at least record who is accessing it. In
addition, I would suggest that said Linux system run with SELinux in
"enforcing" mode. That can stop even "root" from updating something, if it
More importantly, what version of PostgreSQL and what O/S are you working
with.
If this is Ubuntu, you could simply be looking at the wrong postgresql.conf
file.
On Tue, Nov 17, 2015 at 7:33 AM, John McKown
wrote:
> I agree with Adrian. If this is on a Linux
On 11/16/2015 06:59 PM, M Tarkeshwar Rao wrote:
Hi All,
In our production setup we found new issue as postgreSQL.conf has become
zero byte file.
After some time we copied that file from some back up, after some time
it has again become zero byte.
Any clue what is the reason of this behavior.
Hi All,
In our production setup we found new issue as postgreSQL.conf has become zero
byte file.
After some time we copied that file from some back up, after some time it has
again become zero byte.
Any clue what is the reason of this behavior.
Regards
Tarkeshwar
As Andy mentioned. After tuning a query, every thing settled in . Now the
cpu utilization has come down a lot..
Thanks a lot for the help. I will certainly use the tool, pg_top
kind regards
On Fri, Apr 11, 2014 at 12:35 AM, Venkata Balaji Nagothi
vbn...@gmail.comwrote:
On Thu, Apr 10, 2014
On Thu, Apr 10, 2014 at 12:43 AM, Bala Venkat akpg...@gmail.com wrote:
Hi all -
We are running postgres 9.0 ( 32 bit ) + postgis 1.5.2 on Solaris
Sparc M5000 with 64GB . Recently we are getting CPU utilitzation to 99% .
In the config file
shared_buffers=2GB.
work_mem = 128MB
Hi all -
We are running postgres 9.0 ( 32 bit ) + postgis 1.5.2 on Solaris
Sparc M5000 with 64GB . Recently we are getting CPU utilitzation to 99% .
In the config file
shared_buffers=2GB.
work_mem = 128MB
effective_cache_size=48GB
maintaince_work_mem= 500MB
max_connections = 300
When
On 04/09/2014 09:43 AM, Bala Venkat wrote:
Hi all -
We are running postgres 9.0 ( 32 bit ) + postgis 1.5.2 on Solaris Sparc
M5000 with 64GB . Recently we are getting CPU utilitzation to 99% .
In the config file
shared_buffers=2GB.
work_mem = 128MB
effective_cache_size=48GB
Hi,
Which is the quickest way to troubleshot the message
LOG: configuration file /postgresql.conf contains errors;
unaffected changes were applied ?
I made a couple of changes a few days ago, and did not reload Today I made
some more changes and did a pg_ctl reload.
Is there an option to
Jayadevan M maymala.jayade...@gmail.com writes:
Which is the quickest way to troubleshot the message
LOG: configuration file /postgresql.conf contains errors;
unaffected changes were applied ?
There should be log message(s) before that one complaining about the
specific problems.
Thanks. This is what I have. May be it is not really an error?
2013-10-18 12:23:54.996 IST,,,8855,,523c23ea.2297,20,,2013-09-20 16:01:06
IST,,0,LOG,0,received SIGHUP, reloading configuration files,
2013-10-18 12:23:54.996 IST,,,8855,,523c23ea.2297,21,,2013-09-20 16:01:06
On Fri, Oct 18, 2013 at 2:01 PM, Jayadevan M maymala.jayade...@gmail.comwrote:
Thanks. This is what I have. May be it is not really an error?
2013-10-18 12:23:54.996 IST,,,8855,,523c23ea.2297,20,,2013-09-20 16:01:06
IST,,0,LOG,0,received SIGHUP, reloading configuration files,
I've got a question relating to how the postgres configuration is parsed:
If I write into the following into postgresql.conf:
shared_buffers = 24MB
shared_buffers = 32MB
and start up postgres, the command 'show shared_buffers;' answers
'32MB'. That means the later value in the configuration
On 03/21/2012 07:02 AM, Martin Gerdes wrote:
I've got a question relating to how the postgres configuration is parsed:
If I write into the following into postgresql.conf:
shared_buffers = 24MB
shared_buffers = 32MB
and start up postgres, the command 'show shared_buffers;' answers
'32MB'. That
Hi,
I've two questions.
(1) I updated logging_collector = true in postgresql.conf because I want to
rotate the logs. I'd also like to set the log_min_message to 'debug5' so that
I can better debug the code for now and will change it back to a lower level
when it's in production. I'm looking
Wang, Mary Y wrote:
(1) I updated logging_collector = true in postgresql.conf because I want to
rotate the logs. I'd also like to set the log_min_message to 'debug5' so that
I can better debug the code for now and will change it back to a lower level
when it's in production. I'm looking at
Hi,
I have a slow response of my PostgreSQL database 7.4 using this query below
on a table with 80 rows:
select count(*)from tbl;
PostgreSQL return result in 28 sec every time.
although MS-SQL return result in 0.02 sec every time.
My server is a DELL PowerEdge 2600 with bi-processor Xeon
am Tue, dem 23.01.2007, um 12:11:40 +0100 mailte Laurent Manchon folgendes:
Hi,
I have a slow response of my PostgreSQL database 7.4 using this query below
on a table with 80 rows:
select count(*)from tbl;
How often do you want to ask the very same question?
You have enough answers,
] On Behalf Of A. Kretschmer
Sent: Tuesday, January 23, 2007 6:17 AM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Postgresql.conf
am Tue, dem 23.01.2007, um 12:11:40 +0100 mailte Laurent Manchon
folgendes:
Hi,
I have a slow response of my PostgreSQL database 7.4 using this query
below
am Tue, dem 23.01.2007, um 10:12:13 -0500 mailte Brandon Aiken folgendes:
Out of curiosity, has the COUNT(*) with no WHERE clause slowness been
fixed in 8.x? Or is it still an issue of there's no solution that
won't harm aggregates with WHERE clauses?
I will try it:
scholl=# \timing
Timing
A. Kretschmer schrieb:
am Tue, dem 23.01.2007, um 10:12:13 -0500 mailte Brandon Aiken folgendes:
Out of curiosity, has the COUNT(*) with no WHERE clause slowness been
fixed in 8.x? Or is it still an issue of there's no solution that
won't harm aggregates with WHERE clauses?
I will try it:
On Tue, Jan 23, 2007 at 10:12:13 -0500,
Brandon Aiken [EMAIL PROTECTED] wrote:
Out of curiosity, has the COUNT(*) with no WHERE clause slowness been
fixed in 8.x? Or is it still an issue of there's no solution that
won't harm aggregates with WHERE clauses?
Probably not in the sense that you
But there are ways that we could optimize count(*) queries for specific
circumstances right? Obviously this isn't trivial, but I think it would
be nice if we could maintain a number of rows count that could be used
when performing a count(*) on the whole table (no where clause).
I don't know
On 1/23/07, Laurent Manchon [EMAIL PROTECTED] wrote:
Hi,
I have a slow response of my PostgreSQL database 7.4 using this query below
on a table with 80 rows:
select count(*)from tbl;
PostgreSQL return result in 28 sec every time.
although MS-SQL return result in 0.02 sec every time.
On Tue, Jan 23, 2007 at 02:15:23PM -0500, Jeremy Haile wrote:
But there are ways that we could optimize count(*) queries for specific
circumstances right? Obviously this isn't trivial, but I think it would
be nice if we could maintain a number of rows count that could be used
when performing
On Tue, Jan 23, 2007 at 14:15:23 -0500,
Jeremy Haile [EMAIL PROTECTED] wrote:
But there are ways that we could optimize count(*) queries for specific
circumstances right? Obviously this isn't trivial, but I think it would
be nice if we could maintain a number of rows count that could be used
Andreas,
Would you mind explaining what you mean by localized object names and why it
might be bad? Or where I might go to learn more?
Thanks,
-Ben
On Tuesday 23 January 2007 07:38, Tino Wildenhain wrote:
A. Kretschmer schrieb:
am Tue, dem 23.01.2007, um 10:12:13 -0500 mailte Brandon
am Tue, dem 23.01.2007, um 20:48:28 -0800 mailte Benjamin Smith folgendes:
Andreas,
Would you mind explaining what you mean by localized object names and why
it
might be bad? Or where I might go to learn more?
Thanks,
Tino wrote this ;-)
Btw.: Fullquote below make its harder to
Jim, list,from your link:ttp://www.varlena.com/GeneralBits/Tidbits/annotated_conf_e.html
I quote:As a rule of thumb,
observe shared memory usage of PostgreSQL with
tools like ipcs and determine the setting. Remember that this is
only half the story. You also need to set
On Oct 11, 2006, at 03:34 , Jim C. Nasby wrote:
And increase estimated_cache_size to something close
to how much memory you have.
That would be effective_cache_size.
Alexander.
---(end of broadcast)---
TIP 6: explain analyze is your friend
Please take a look at
http://www.varlena.com/GeneralBits/Tidbits/annotated_conf_e.html first.
In a nutshell, set shared_buffers to between 10% and 25% of your memory
if it's a server. And increase estimated_cache_size to something close
to how much memory you have.
On Tue, Oct 03, 2006 at
Hi all,
- What does the shared_buffers setting do ?
- Does it mean that that the postgres cannot access most of the physical RAM
but limited to the memory setting (shared_buffers) specified ?
- How do i relate and set max_connections and shared_buffers?
- Is there a thumb rule to determine
I recently have been attempting to get my install of postgresql 8.1
(running Win XP as OS) to listen on both 127.0.0.1 and my IP address,
192.168.0.100 (inside my network, obviously.) As such, I tried first
setting listen_addresses = '192.168.0.100, localhost'
With it like that, when I try to
On 3/29/06, David Bernal [EMAIL PROTECTED] wrote:
I recently have been attempting to get my install of postgresql 8.1
(running Win XP as OS) to listen on both 127.0.0.1 and my IP address,
192.168.0.100 (inside my network, obviously.) As such, I tried first
setting listen_addresses =
David Bernal [EMAIL PROTECTED] writes:
I recently have been attempting to get my install of postgresql 8.1
(running Win XP as OS) to listen on both 127.0.0.1 and my IP address,
192.168.0.100 (inside my network, obviously.) As such, I tried first
setting listen_addresses = '192.168.0.100,
On Wednesday 29 March 2006 02:59 am, David Bernal wrote:
Any ideas? I'm fairly baffled, but then I'm a newbie.
Just a thought, did you restart the server after making the changes?
From the Postgres docs-
...This parameter can only be set at server start.
--
Adrian Klaver
[EMAIL
Try * (wildcard) and see what happens. It should either work or not
work, not work 'sometimes' so I think there must be something else
involved. If pg_hba.conf is set up right, and listen address is *
then you have the network to look at.
I actually also did try '*', and it actually did
Just a thought, did you restart the server after making the changes?
From the Postgres docs-
...This parameter can only be set at server start.
Sure did, each and every time.
On 3/29/06, Adrian Klaver [EMAIL PROTECTED] wrote:
On Wednesday 29 March 2006 02:59 am, David Bernal wrote:
Any
By 8.1 do you really mean 8.1.0? If so, you might try updating to
the latest subrelease (currently 8.1.3). This problem doesn't offhand
seem to match any of the bug fixes I see in the CVS logs, but there have
been a number of Windows-specific fixes and maybe one of them explains
it.
Yeah,
folks
what is preferible value for
stats_reset_on_server_start ?
what is default value?
best regards
MDC
__
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam ¡gratis!
¡Abrí tu cuenta ya! - http://correo.yahoo.com.ar
On Wed, 2005-08-03 at 13:30 -0300, marcelo Cortez wrote:
folks
what is preferible value for
stats_reset_on_server_start ?
depends on whether you want stats to be accumulated for longer periods
than between restarts. I imagine that 'on' is what most people need.
in any case, you can reset
Yes I removed the comment...
Tail end of postgresql.conf..
#---
# VERSION/PLATFORM COMPATIBILITY
#---
# - Previous Postgres Versions -
# do not
Niederland wrote:
postgres does not seem to pick up
the following parameter in the postgresql.conf
add_missing_from = false
Setting the parameter via psql, functions properly
SET add_missing_from TO FALSE
Using: winxp, Postges 8.0
(note: I did restart the service after updating the
postgres does not seem to pick up
the following parameter in the postgresql.conf
add_missing_from = false
Setting the parameter via psql, functions properly
SET add_missing_from TO FALSE
Using: winxp, Postges 8.0
(note: I did restart the service after updating the parameters in
postgresql.conf)
Hey Guys,
I am setting up a new dedicated Postgres server, and will serve about
60 databases to a web site serving 250,000 people at the rate of about
20,000 a day. That may all be irrellevent though for the purposes of
this conversation.
The main thing about the application is that we're
On Wed, 2004-12-22 at 09:15, John Cunningham wrote:
Hey Guys,
I am setting up a new dedicated Postgres server, and will serve about
60 databases to a web site serving 250,000 people at the rate of about
20,000 a day. That may all be irrellevent though for the purposes of
this conversation.
John Cunningham wrote:
...
The machine in question will do nothing but serve databases. It's a
dual 3.2Ghz Xeon with 100GB or 15K RPM RAID 5 and 8 GB of RAM. I'd
like to configure it to get the most out of the server possible as far
as shared memory, sort memore, etc. I haven't found a lot of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Dec 22, 2004, at 10:15 AM, John Cunningham wrote:
like to configure it to get the most out of the server possible as far
as shared memory, sort memore, etc. I haven't found a lot of
documentation on this.
I'm running Red Hat Enterprise ES with all the most recent updates.
The error - in initdb - was that the system couldn't find
ascii_and_mic libraries. 7.3.6 ran without a hitch.
The RAID 1+0 - is that a stripped / mirrored condifuration? How big
of a difference will that make in performance do
On Wed, 22 Dec 2004 10:38:01 -0600, John Cunningham [EMAIL PROTECTED] wrote:
I'm running Red Hat Enterprise ES with all the most recent updates.
The error - in initdb - was that the system couldn't find
ascii_and_mic libraries. 7.3.6 ran without a hitch.
That's very odd, cause I'm using
OK Guys - here's the config file as I've writtten it.
I'll paste in the whole thing before, but this is the important stuff:
max_connections = 256
shared_buffers = 32768 # (256 MB)
sort_mem = 1024 # min 64, size in KB
fsync = No
wal_sync_method = fsync # the default varies across platforms:
On Wed, 2004-12-22 at 11:30, John Cunningham wrote:
OK Guys - here's the config file as I've writtten it.
I'll paste in the whole thing before, but this is the important stuff:
max_connections = 256
Are you using a connection pooling scheme (jdbc based pooling, pgpool,
etc...)? If not,
The server is a DELL Poweredge 2650 with it's built in RAID - 4 disks
currently in a RAID 5 config. I will check on the battery backup.
I'm putting this server together and rebuilding our overall db
structure all at the same time, so I have a good amount of flexiblity.
I realized I was not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Dec 22, 2004, at 2:36 PM, John Cunningham wrote:
The shared buffers was a big concern - I've read that there's a limit
that helps, but as the machine will only do DB transactions, I don't
know what else to do with the RAM. It's intended for PG's
John Cunningham [EMAIL PROTECTED] writes:
The shared buffers was a big concern - I've read that there's a limit
that helps, but as the machine will only do DB transactions, I don't
know what else to do with the RAM. It's intended for PG's use.
The kernel will use it for disk caching which
PROTECTED]
To: Mihai Gheorghiu [EMAIL PROTECTED]; [EMAIL PROTECTED]
[EMAIL PROTECTED]
Date: Tuesday, September 25, 2001 8:30 PM
Subject: Re: [GENERAL] postgresql.conf
On Tuesday 25 September 2001 11:34 am, Mihai Gheorghiu wrote:
I installed PG from RPMs. postgresql.conf comes with all options
I installed PG from RPMs. postgresql.conf comes with all options commented
out.
What are the defaults? PG works anyway (Well... I know... -i etc.)
Thank you all.
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
On Tuesday 25 September 2001 11:34 am, Mihai Gheorghiu wrote:
I installed PG from RPMs. postgresql.conf comes with all options commented
out.
What are the defaults? PG works anyway (Well... I know... -i etc.)
Thank you all.
All options commented out is the installation default of a
hafiz writes:
I use Postgresql 7.0.3-2 in red-hat 6.2
I change several postmaster options through postgresql.conf (in
/usr/local/pgsql/data) . But it seems
that the postmaster still run using default values and ignored
postgresql.conf. I've check the file permission and it should be ok.
hafiz wrote:
I use Postgresql 7.0.3-2 in red-hat 6.2
I change several postmaster options through postgresql.conf (in
/usr/local/pgsql/data) . But it seems
that the postmaster still run using default values and ignored
postgresql.conf. I've check the file permission and it should be ok.
64 matches
Mail list logo