On 02/24/2013 10:05 PM, Jeff Frost wrote:
>
> On Feb 24, 2013, at 7:16 AM, Rafael Martinez Guerrero
> mailto:r.m.guerr...@usit.uio.no>> wrote:
>
>> We reported this back in 2011, but we did not get to any conclusion:
>> http://www.postgresql.org/message-id/4de8907
rested in this subject because we have had this problem a few
times. But we have not been able to identify the reason that triggers this.
regards,
--
Rafael Martinez Guerrero
Center for Information Technology
University of Oslo, Norway
PGP Public Key: http://folk.uio.no/rafael/
--
Sent via pg
it to
/dev/null is not an option to us.
truncate_on_rotation for us outside the development world of postgres,
means that, the file will get truncated on rotation independently of
the filename schema used.
Thanks for your time.
regards,
- --
Rafael Martinez Guerrero
Center for Information T
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/19/2013 11:21 AM, Tom Lane wrote:
> Rafael Martinez writes:
>> If the behavior we are talking about is intentional, why do be
>> have pg_rotate_logfile() if we can not manually override with
>> this function
n.
Here PostgreSQL is versatile enough to let you define the name of the
log file in many ways so you can control if the number of "old" files
grow indefinitely or not.
Thanks for your time.
regards,
- --
Rafael Martinez Guerrero
Center for Information Technology
University of
append to, any existing log file of the same name ..."
"... pg_rotate_logfile signals the log-file manager to switch to a new
output file immediately"
regards,
- --
Rafael Martinez Guerrero
Center for Information Technology
University of Oslo, Norway
PGP Public Key: htt
t maybe if you can avoid running
vacuum full unnecessarily, you will also avoid this problem you are
experiencing.
regards
--
Rafael Martinez,
Center for Information Technology Services
University of Oslo, Norway
PGP Public Key: http://folk.uio.no/rafael/
--
Sent via pgsql-bugs mailing list (
;
> The reported object is an index.
> The size of its data file is 630784 bytes.
>
Hello
You have probably a harware issue and data in your disk is corrupted.
Probably a reindex of this index will fix this problem. But I would take
a backup of this system right away just in case your
oop () at postmaster.c:1119
#14 0x0812d305 in PostmasterMain (argc=3, argv=0x826e1c0) at
postmaster.c:897
#15 0x08104f10 in main (argc=3, argv=0xbfffd6c4) at main.c:214
We are currently in the process of moving the production server to an
IBM box, which should eliminate any Dell2650 spesific ca
On Tue, 2004-09-07 at 23:36, Tom Lane wrote:
> Rafael Martinez <[EMAIL PROTECTED]> writes:
> > I got this from one of our developers (from the core dump generated by
> > 7.3.7 without --enable-debug):
>
> > (gdb) inspect *att[i]
> > $3 = {attrelid = 0, attname
On Tue, 2004-09-07 at 19:58, Tom Lane wrote:
> Rafael Martinez Guerrero <[EMAIL PROTECTED]> writes:
> > * Information from CORE dump we got with --enable-debug. We have
> > compiled a new version of postgres and run it through gdb with the core
> > dump we had/got fro
[8100] LOG: statement: CLOSE "PgSQL_083326D4"
2004-09-07 15:58:54 [8100] LOG: statement: CLOSE "PgSQL_083326D4"
2004-09-07 15:58:54 [8100] LOG: statement: CLOSE "PgSQL_083326D4"
2004-09-07 15:58:54 [8100] LOG: statement: DECLARE "PgSQL_083326D4"
CURSOR FOR SELECT code FROM quarantine_code WHERE code_str =
'nologin_stengt'
2004-09-07 15:58:54 [8100] LOG: statement: DECLARE "PgSQL_083326D4"
CURSOR FOR SELECT code FROM quarantine_code WHERE code_str =
'nologin_stengt'
2004-09-07 15:58:54 [8100] LOG: statement: DECLARE "PgSQL_083326D4"
CURSOR FOR SELECT code FROM quarantine_code WHERE code_str =
'nologin_stengt'
2004-09-07 15:58:54 [8100] LOG: statement: CLOSE "PgSQL_083326D4"
2004-09-07 15:58:54 [8100] LOG: statement: CLOSE "PgSQL_083326D4"
2004-09-07 15:58:54 [8100] LOG: statement: CLOSE "PgSQL_083326D4"
2004-09-07 15:58:54 [8100] LOG: statement: DECLARE "PgSQL_083326D4"
CURSOR FOR SELECT code FROM quarantine_code WHERE code_str =
'svakt_passord'
2004-09-07 15:58:54 [8100] LOG: statement: DECLARE "PgSQL_083326D4"
CURSOR FOR SELECT code FROM quarantine_code WHERE code_str =
'svakt_passord'
2004-09-07 15:58:54 [8100] LOG: statement: DECLARE "PgSQL_083326D4"
CURSOR FOR SELECT code FROM quarantine_code WHERE code_str =
'svakt_passord'
2004-09-07 15:58:54 [8100] LOG: statement: CLOSE "PgSQL_083326D4"
2004-09-07 15:58:54 [8100] LOG: statement: CLOSE "PgSQL_083326D4"
2004-09-07 15:58:54 [8100] LOG: statement: CLOSE "PgSQL_083326D4"
2004-09-07 15:58:54 [8100] LOG: statement: DECLARE "PgSQL_083326D4"
CURSOR FOR SELECT code FROM quarantine_code WHERE code_str = 'nologin'
2004-09-07 15:58:54 [8100] LOG: statement: DECLARE "PgSQL_083326D4"
CURSOR FOR SELECT code FROM quarantine_code WHERE code_str = 'nologin'
2004-09-07 15:58:54 [8100] LOG: statement: DECLARE "PgSQL_083326D4"
CURSOR FOR SELECT code FROM quarantine_code WHERE code_str = 'nologin'
--
Thanks in advance, any help will be appreciated.
--
Rafael Martinez, <[EMAIL PROTECTED]>
Center for Information Technology Services
University of Oslo, Norway
signature.asc
Description: This is a digitally signed message part
12 matches
Mail list logo
