Evan Rempel wrote:
> Well, the list became very quiet on this question. Can anyone chime in with
> suggestions to have some accounts authenticated by ldap and the remainder by
> MD5
Create a group/role and list that in pg_hba.conf for each authentication
method.
-
"Scott Marlowe" <[EMAIL PROTECTED]> writes:
> Template0 is your "man, I really screwed up template1" get out of jail
> free database. It is normally set to not allow connections (look at
> "select * from pg_databases;" for the field that does or doesn't allow
> connections). If you ever did terri
On Thu, Oct 9, 2008 at 12:56 PM, Marc Fromm <[EMAIL PROTECTED]> wrote:
> I started logging on our server. There are many entries like this:
>
> transaction ID wrap limit is 1073768178, limited by database "postgres"
>
> transaction ID wrap limit is 1073771864, limited by database "sms"
>
> Each dat
Evan Rempel wrote:
> What this means is that you do not have to "update" the data repository
> (wherever your
> postgresql database is stored). All that needs to be done is to uninstall the
> old version,
> and install the new version. Start the new version and use the data where it
> sits.
Act
What this means is that you do not have to "update" the data repository
(wherever your
postgresql database is stored). All that needs to be done is to uninstall the
old version,
and install the new version. Start the new version and use the data where it
sits.
Now, that all sound fine when I s
What this means is that you do not have to "update" the data repository
(wherever your
postgresql database is stored). All that needs to be done is to uninstall the
old version,
and install the new version. Start the new version and use the data where it
sits.
Now, that all sound fine when I s
What this means is that you do not have to "update" the data repository
(wherever your
postgresql database is stored). All that needs to be done is to uninstall the
old version,
and install the new version. Start the new version and use the data where it
sits.
Now, that all sound fine when I s
Hello,
I'm doing an upgrade from 8.2.4 to 8.2.10. The documentation says,
"When you update between compatible versions, you can simply replace
the executables and reuse the data directory on disk." I guess I
don't quite understand what this means. Replace them by running some
parts of
Hi,
We have a read-only database with large BLOBs, and the field
'xact_commit' of pg_stat_database is incremented by thousands every minute.
The number of concurrent connections is about 5-10.
What is considered a transaction in general and when BLOBs are involved
and how does it affect the au
"Martin A. Brooks" <[EMAIL PROTECTED]> writes:
> I don't explicitly set that parameter in my config. The full config
> file can be found at http://www.antibodymx.net/postgresql.conf
You've got log_duration on; that overrides log_min_duration_statement
and forces statement durations to always be
Vladimir Rusinov wrote:
May be you have log_min_messages = debug?
Please, show full logging section.
I don't explicitly set that parameter in my config. The full config
file can be found at http://www.antibodymx.net/postgresql.conf
Thanks
--
Martin A. Brooks | http://www.antibodymx.net/
On Tue, Oct 14, 2008 at 1:23 PM, Martin A. Brooks <[EMAIL PROTECTED]>wrote:
> Hi
>
> I want to have postgres log sql statements that take longer than 5 seconds
> to execute. In postgresql.conf I have set log_min_duration_statement as
> follows:
>
> [EMAIL PROTECTED]:/etc/postgresql/8.3/main# grep
Guillaume Lelarge wrote:
Martin A. Brooks a écrit :
I _want_ the stats, however I _only_ want the stats for queries taking
over 5 seconds.
Well, AFAIK, you can't.
Then that would seem to entirely negate the point of having the
log_min_duration_statement option, from what I can s
Martin A. Brooks a écrit :
> Guillaume Lelarge wrote:
>> Martin A. Brooks a écrit :
>>
>>> However, in the log files, I'm seeing entries for all SQL executed, not
>>> just that taking 5000ms or more. For example:
>>>
>>> 2008-10-14 10:15:50 BST PID:20349 DB:vhdb LOG: statement: select * from
>>>
Guillaume Lelarge wrote:
Martin A. Brooks a écrit :
However, in the log files, I'm seeing entries for all SQL executed, not
just that taking 5000ms or more. For example:
2008-10-14 10:15:50 BST PID:20349 DB:vhdb LOG: statement: select * from
vendors;
2008-10-14 10:15:50 BST PID:20349 DB:vhd
Martin A. Brooks a écrit :
> Hi
>
> I want to have postgres log sql statements that take longer than 5
> seconds to execute. In postgresql.conf I have set
> log_min_duration_statement as follows:
>
> [EMAIL PROTECTED]:/etc/postgresql/8.3/main# grep log_min_duration
> postgresql.conf
> log_min_du
Hi
I want to have postgres log sql statements that take longer than 5
seconds to execute. In postgresql.conf I have set
log_min_duration_statement as follows:
[EMAIL PROTECTED]:/etc/postgresql/8.3/main# grep log_min_duration
postgresql.conf
log_min_duration_statement = 5000 # -1 is di
17 matches
Mail list logo
