It depends on the database transactional activity,
observe how many new wal files are generated during a period equivalent to
what it takes to do your base backup. I would set it to twice that number.
Take into account that a checkpoint is issued at the beginning of the
process. If you're lazy just
On Monday, June 23, 2014, AI Rumman > wrote:
> Could someone please tell me why I am getting these in my log:
>
> 2014-06-23 00:00:00.031 CDT [11379][@] : [1-1]LOG: skipping analyze of
> "table1" --- lock not available
> 2014-06-23 00:00:00.056 CDT [11380][@] : [1-1]LOG: skipping analyze of
> "t
AI Rumman wrote:
> Could someone please tell me why I am getting these in my log:
>
> 2014-06-23 00:00:00.031 CDT [11379][@] : [1-1]LOG: skipping analyze of
> "table1" --- lock not available
Enough activity has accumulated on table1 that it is due for new
statistics, but when autovacuum tried
As far as I'm concerned, you cannot inherit role settings, only privileges.
http://www.postgresql.org/docs/9.3/static/role-membership.html
2014-06-23 20:12 GMT-05:00 Rene Romero Benavides :
> To impersonate another role, as a superuser or group member use:
> SET SESSION AUTHORIZATION user1;
>
>
To impersonate another role, as a superuser or group member use:
SET SESSION AUTHORIZATION user1;
http://www.postgresql.org/docs/9.3/static/sql-set-session-authorization.html
Regards.
2014-06-23 8:25 GMT-05:00 McGehee, Robert :
> Hi,
>
> I'm trying to set the default statement_timeout paramete
Could someone please tell me why I am getting these in my log:
2014-06-23 00:00:00.031 CDT [11379][@] : [1-1]LOG: skipping analyze of
"table1" --- lock not available
2014-06-23 00:00:00.056 CDT [11380][@] : [1-1]LOG: skipping analyze of
"table1" --- lock not available
2014-06-23 00:00:00.081 CDT
"McGehee, Robert" writes:
> I'm trying to set the default statement_timeout parameter for two different
> groups of users. However, as many of the users inherit from overlapping
> roles, I wanted to get clarification on how inheritance of parameter values
> worked when a role inherits from othe
Hi all,
Can I do a consistent file-system-level backup using the following
procedure:
1) SELECT pg_start_backup(...)
2) rsync postgres data dir to another server
3) SELECT pg_stop_backup()
4) rsync pg_xlog directory
From what I understand this should be similar to running pg_basebackup
using th
Hi,
I'm trying to set the default statement_timeout parameter for two different
groups of users. However, as many of the users inherit from overlapping roles,
I wanted to get clarification on how inheritance of parameter values worked
when a role inherits from other roles that all have different
On Sun, Jun 22, 2014 at 9:49 AM, Vito wrote:
> Hi all,
>
> I'm interested in the development of postgreSQL. But I think reading the
> whole document will take a long time.
Are you referring to the user documentation, or the developer documentation?
The user documentation is pretty good, and you
Hi,
I have here a question concerning how ACLs are handled for Types.
For Tables, when Ownership changes, Grantor info is also changed; hence
changing Ownership and Grants does not lead to the same privilege but from
different Grantors.
For Types though, you can easily end up with an ACL like {use
Thanks, I'll try to go through it.
At 2014-06-23 10:56:39, "Adrian Klaver" wrote:
>On 06/22/2014 07:16 PM, Vito wrote:
>> Thanks for your detailed information! Do you think the official document
>> is the best way to get to know about PostgreSQL?
>>
>
>AFAIK it is the only way, especially if you
Arup Rakshit wrote:
> yelloday-staging::YELLOW=> select id, dob from users;
> id | dob
> +-
> 13 |
> 9 | 1967-02-13 14:00:00
> 10 |
> 11 |
> 8 | 1977-06-05 14:00:00
> 15 |
> 21 |
> 14 | 2014-05-25 14:00:00
> 37 |
> 22 |
> 26 | 2014-05-06 14:00:00
> 32
Hi,
thanks for replying.
Yes, I've seen that information in that file was introduced by initdb
initially. When I restart the server/PGSQL it appends/adds information to
that file, wihout modifying information that was introduced initially by
initdb .. so I'm sure that initdb was executed only once.
Look the below 2 scenarios :-
yelloday-staging::YELLOW=> select id, dob from users;
id | dob
+-
13 |
9 | 1967-02-13 14:00:00
10 |
11 |
8 | 1977-06-05 14:00:00
15 |
21 |
14 | 2014-05-25 14:00:00
37 |
22 |
26 | 2014-05-06 14:00:00
32 |
15 matches
Mail list logo