select current_user;
On Thu, Jan 30, 2014 at 3:53 PM, Adrian Klaver wrote:
> On 01/30/2014 06:13 AM, Ovid wrote:
>
>> First: CREATE ROLE and CREATE DATABASE;
>>>
>>
>> After: CREATE TABLEs;
>>>
>>
>> Last: GRANT SELECT,INSERT,UPDATE and DELETE.
>>>
>>
>> OK, I dropped the database. Since I hav
well, in your statement, the parameters are missing.
2013-08-05 10:18:01 STATEMENT: select distinct count(*) as rownum from
minta as m join partner as p on ( m.partnerid = p.partnerid ) join
mintajelleg as mj on ( mj.mintajellegid = m.mintajellegid ) where
m.status IN and m.mintajellegid =
No, it's super frustrating. While I do the recovery, it says it reaches a
consistent recovery state, and i just cannot find a way how to convince pg
to stop at that state:
2013-08-02 09:23:25 GMT DEBUG: postgres: PostmasterMain: initial
environment dump:
2013-08-02 09:23:25 GMT DEBUG:
29:09 UTC <%> LOG: database system is ready to accept
connections
well, that does not indicate anything for me.
On Wed, Jul 31, 2013 at 9:37 AM, Albe Laurenz wrote:
> Klaus Ita wrote:
> > I have restored a Database Cluster with a recovery_target_time set to
> >
> >
Hello PG Experts!
I have restored a Database Cluster with a recovery_target_time set to
recovery_target_time = '2013-07-27 21:20:17.127664+00'
recovery_target_inclusive = false
now it seems the restore rather restored to some point in time (rather the
18th than the 27th). Is there an explanati
7;s an lsi
controller, ... not fond of it, but it's not bad stuff.
lg,k
On Tue, Jul 30, 2013 at 5:29 PM, bricklen wrote:
>
> On Tue, Jul 30, 2013 at 8:18 AM, Klaus Ita wrote:
>
>>
>> thank you! It turned out that really there was a corruption in the main
>> pg server
7;d be safe.
lg,k
On Tue, Jul 30, 2013 at 5:13 PM, bricklen wrote:
> On Mon, Jul 29, 2013 at 11:50 PM, Klaus Ita wrote:
>
>> I am trying to remember, there was a tool that plotted the contents of
>> the wal_files in a more readable format ...
>>
>
> xlogdump?
>
> https://github.com/snaga/xlogdump
>
ly
session-logging/statistics data).
I am trying to remember, there was a tool that plotted the contents of the
wal_files in a more readable format ...
lg,k
On Tue, Jul 30, 2013 at 8:23 AM, raghu ram wrote:
>
> On Tue, Jul 30, 2013 at 4:07 AM, Klaus Ita wrote:
>
>> Sorry for cros
Hi List!
On an originally designated hot_standby that had been not so hot for the
last 24h i tried to replay the wal_files left over from a (seemingly
corrupted) master server [missing clog... ].
I get this output:
"/etc/postgresql/9.1/main/postgresql.conf" 584L, 19942C written
root@pgstandby7:/
Sorry for cross-posting, i read that pg-bug was not the right place for
this email
Hi list!
depressed me gets error messages like these:
2013-07-29 20:57:09 UTC ERROR: could not access
status of transaction 8393477
2013-07-29 20:57:09 UTC DETAIL: Could not open
file "pg_clog/0008": No such f
10 matches
Mail list logo
