is it bug

Поиск
Список
Период
Сортировка
От
Тема	is it bug
Дата	11 декабря 2004 г. 20:54:28
Msg-id	20041208114326.8AB9D5B0B21@svr4.postgresql.org обсуждение исходный текст
Ответы	Re: is it bug (Tom Lane <tgl@sss.pgh.pa.us>)
Список	pgsql-bugs
Дерево обсуждения
Hi when i start this SQL on windows postgres rc1

select fi.ID_PGODINE,fi.ID_OZNAKE_OTPREME,fi.ID_FAKTURE_IZLAZNA,OZN_KP,fi.OZN_VAL_NBJ_STR AS ID_ZEMLJE,ug.ID_UGOVORA,
       ug.NAP_UGOVORA,fn.TEKST_NAPOMENE,kat.NAZIV_ELEM,
CASE fakt_lit
    WHEN 'Y' THEN  'L'
    ELSE kat.JM
    END as JM,
npl.OPIS_NACINA_PLACANJA,p.ID_POREZA,

p.OPIS_POREZA,p.PROC_POREZA,p.POREZ_JE_ZA_USLUGU,pp.NAZ_PARTNERA,pp.ULICA_PP,pp.ADR_PP,pr.NAZ_PRIMAOCA,rd1.PRZ_RADNIKA
ASPRZFKT, 
       rd1.IME_RADNIKA AS IMEFKT,rd2.PRZ_RADNIKA AS PRZSEF,rd2.IME_RADNIKA AS IMESEF,fi.ZIRO_RAC,DAT_KP AS
DATUM_IZF,fi.DAT_OTPREME,
       fi.ROK_PLACANJA,(fi.DATUM_IZF+fi.ROK_PLACANJA) AS
ROKDATUM,fi.IZJAVA_BR,fi.DAT_IZJAVE,fi.br_zaklj,fi.br_inof,fi.kurs,fi.NAP_IZF,fi.JE_FAKTURA,fi.OZN_VAL_NBJ_STRAS
ID_VALUTE,
       sfi.RBR_STAVKE_FI,null as AkcizaProc,
skp.KOL_KP as KOL_FI,
coalesce(skp.uk_roba_kp,0) as vrobe,
coalesce(skp.uk_akciza_din_kp,0) as AkcizaDin,
coalesce(skp.uk_man_tr_kp,0) as mantr,
coalesce(skp.uk_marza_kp,0) as marza,
coalesce(pskp.uk_porez,0) as Porez
from FAKTURA_IZLAZNA fi LEFT OUTER JOIN UGOVOR ug
    ON(fi.ID_UGOVORA = ug.ID_UGOVORA)
    LEFT OUTER JOIN Valuta zm
    ON(fi.OZN_VAL_NBJ_STR = zm.OZN_VAL_NBJ_STR),
     PRIMAOC pr,
     POSLOVNI_PARTNER pp,
     NACIN_PLACANJA npl,
     KORISNIK ko1,
     KORISNIK ko2,
     RADNIK rd1,
     RADNIK rd2,
     STAVKA_FAKTURE_IZLAZNE sfi,
     KATALOG kat,
     KNJIZNO_PISMO kp    LEFT OUTER JOIN FAKTURA_NAPOMENA fn
    ON (kp.ID_NAPOMENA = fn.ID_NAPOMENA),
     STAVKA_KP skp LEFT OUTER JOIN porez_skp pskp
        ON (skp.id_pgodine = pskp.id_pgodine and
        skp.id_oznake_otpreme = pskp.id_oznake_otpreme and
        skp.id_fakture_izlazna = pskp.id_fakture_izlazna and
        skp.id_knj_pisma = pskp.id_knj_pisma and
        skp.rbr_stavke_fi = pskp.rbr_stavke_fi)
        LEFT OUTER JOIN porez p
        ON (pskp.id_poreza = p.id_poreza)
WHERE
    fi.ID_PGODINE = :ID_PGODINE AND
    fi.ID_OZNAKE_OTPREME = :ID_OZNAKE_OTPREME AND
    fi.ID_FAKTURE_IZLAZNA = :ID_FAKTURE_IZLAZNA AND
    fi.ID_PRIMAOCA = pr.ID_PRIMAOCA AND
    fi.ID_PARTNERA = pp.ID_PARTNERA AND
    fi.ID_NACINA_PLACANJA = npl.ID_NACINA_PLACANJA AND
    fi.ID_KORISNIKA = ko1.ID_KORISNIKA AND
    ko1.ID_RADNIKA = rd1.ID_RADNIKA AND
    fi.ID_SEFA = ko2.ID_KORISNIKA AND
    ko2.ID_RADNIKA = rd2.ID_RADNIKA AND
    fi.ID_PGODINE = sfi.ID_PGODINE AND
    fi.ID_OZNAKE_OTPREME = sfi.ID_OZNAKE_OTPREME AND
    fi.ID_FAKTURE_IZLAZNA = sfi.ID_FAKTURE_IZLAZNA AND
    fi.JE_FAKTURA = 'Y' AND
    sfi.ID_ELEMENTA = kat.ID_ELEMENTA AND
    fi.ID_PGODINE = kp.ID_PGODINE AND
    fi.ID_OZNAKE_OTPREME = kp.ID_OZNAKE_OTPREME AND
    fi.ID_FAKTURE_IZLAZNA = kp.ID_FAKTURE_IZLAZNA AND
    kp.ID_KNJ_PISMA = :ID_KNJ_PISMA AND
    kp.ID_KNJ_PISMA = skp.ID_KNJ_PISMA AND
    sfi.ID_PGODINE = skp.ID_PGODINE AND
    sfi.ID_OZNAKE_OTPREME = skp.ID_OZNAKE_OTPREME AND
    sfi.ID_FAKTURE_IZLAZNA = skp.ID_FAKTURE_IZLAZNA AND
    sfi.RBR_STAVKE_FI = skp.RBR_STAVKE_FI
ORDER BY fi.ID_PGODINE,fi.ID_OZNAKE_OTPREME,fi.ID_FAKTURE_IZLAZNA,
        sfi.RBR_STAVKE_FI,
        p.ID_POREZA

postgres crash log look like

2004-12-07 21:05:41 DEBUG:  waiting on 6 children
2004-12-07 21:05:41 DEBUG:  server process (PID 744) was terminated by signal 5
2004-12-07 21:05:41 LOG:  server process (PID 744) was terminated by signal 5
2004-12-07 21:05:41 LOG:  terminating any other active server processes
2004-12-07 21:05:41 DEBUG:  sending SIGQUIT to process 1052
2004-12-07 21:05:41 DEBUG:  sending SIGQUIT to process 1152
2004-12-07 21:05:41 WARNING:  terminating connection because of crash of another server process
2004-12-07 21:05:41 DETAIL:  The postmaster has commanded this server process to roll back the current transaction and
exit,because another server process exited abnormally and possibly corrupted shared memory. 
2004-12-07 21:05:41 HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2004-12-07 21:05:41 DEBUG:  sending SIGQUIT to process 856
2004-12-07 21:05:41 WARNING:  terminating connection because of crash of another server process
2004-12-07 21:05:41 DETAIL:  The postmaster has commanded this server process to roll back the current transaction and
exit,because another server process exited abnormally and possibly corrupted shared memory. 
2004-12-07 21:05:41 HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2004-12-07 21:05:41 DEBUG:  sending SIGQUIT to process 732
2004-12-07 21:05:41 DEBUG:  waiting on 5 children
2004-12-07 21:05:41 DEBUG:  waiting on 4 children
2004-12-07 21:05:41 DEBUG:  server process (PID 1052) was terminated by signal 1
2004-12-07 21:05:41 DEBUG:  waiting on 3 children
2004-12-07 21:05:41 DEBUG:  server process (PID 1152) was terminated by signal 1
2004-12-07 21:05:41 DEBUG:  waiting on 2 children
2004-12-07 21:05:41 LOG:  all server processes terminated; reinitializing
2004-12-07 21:05:41 DEBUG:  shmem_exit(0)
2004-12-07 21:05:41 DEBUG:  invoking IpcMemoryCreate(size=10444800)
2004-12-07 21:05:41 DEBUG:  reaping dead processes
2004-12-07 21:05:41 DEBUG:  waiting on 3 children
2004-12-07 21:05:41 DEBUG:  reaping dead processes
2004-12-07 21:05:41 DEBUG:  waiting on 3 children
2004-12-07 21:05:41 DEBUG:  Attaching to 023D0000
2004-12-07 21:05:41 LOG:  database system was interrupted at 2004-12-07 21:05:18 Central Europe Standard Time
2004-12-07 21:05:41 LOG:  checkpoint record is at 0/291EE4A8
2004-12-07 21:05:41 LOG:  redo record is at 0/291EE4A8; undo record is at 0/0; shutdown TRUE
2004-12-07 21:05:41 LOG:  next transaction ID: 17600; next OID: 3933066
2004-12-07 21:05:41 LOG:  database system was not properly shut down; automatic recovery in progress
2004-12-07 21:05:41 DEBUG:  proc_exit(0)
2004-12-07 21:05:41 DEBUG:  shmem_exit(0)
2004-12-07 21:05:41 DEBUG:  exit(0)
2004-12-07 21:05:41 DEBUG:  reaping dead processes
2004-12-07 21:05:41 DEBUG:  waiting on 3 children
2004-12-07 21:05:41 DEBUG:  waiting on 2 children
2004-12-07 21:05:41 LOG:  record with zero length at 0/291EE4E8
2004-12-07 21:05:41 LOG:  redo is not required
2004-12-07 21:05:41 LOG:  database system is ready
2004-12-07 21:05:41 DEBUG:  proc_exit(0)
2004-12-07 21:05:41 DEBUG:  shmem_exit(0)
2004-12-07 21:05:41 DEBUG:  exit(0)
2004-12-07 21:05:41 DEBUG:  reaping dead processes
2004-12-07 21:05:41 DEBUG:  waiting on 2 children
2004-12-07 21:05:41 DEBUG:  waiting on 2 children
2004-12-07 21:05:41 DEBUG:  Attaching to 023D0000
2004-12-07 21:37:45 DEBUG:  checkpoint starting
2004-12-07 21:37:45 DEBUG:  postmaster received signal 2
2004-12-07 21:37:45 LOG:  received fast shutdown request
2004-12-07 21:37:45 DEBUG:  proc_exit(0)
2004-12-07 21:37:45 DEBUG:  shmem_exit(0)
2004-12-07 21:37:45 DEBUG:  exit(0)
2004-12-07 21:37:45 DEBUG:  reaping dead processes
2004-12-07 21:37:45 DEBUG:  waiting on 3 children
2004-12-07 21:37:45 DEBUG:  waiting on 2 children
2004-12-07 21:37:45 DEBUG:  checkpoint complete; 0 transaction log file(s) added, 0 removed, 0 recycled
2004-12-07 21:37:45 LOG:  shutting down
2004-12-07 21:37:45 LOG:  database system is shut down
2004-12-07 21:37:45 DEBUG:  proc_exit(0)
2004-12-07 21:37:45 DEBUG:  shmem_exit(0)
2004-12-07 21:37:45 DEBUG:  exit(0)
2004-12-07 21:37:45 DEBUG:  postmaster received signal 2
2004-12-07 21:37:46 DEBUG:  reaping dead processes
2004-12-07 21:37:46 DEBUG:  waiting on 2 children
2004-12-07 21:37:46 DEBUG:  proc_exit(0)
2004-12-07 21:37:46 DEBUG:  shmem_exit(0)
2004-12-07 21:37:46 DEBUG:  exit(0)
2004-12-07 21:37:46 LOG:  logger shutting down
2004-12-07 21:37:46 DEBUG:  proc_exit(0)
2004-12-07 21:37:46 DEBUG:  shmem_exit(0)
2004-12-07 21:37:46 DEBUG:  exit(0)

sql work when i modified this like

select fi.ID_PGODINE,fi.ID_OZNAKE_OTPREME,fi.ID_FAKTURE_IZLAZNA,OZN_KP,fi.OZN_VAL_NBJ_STR AS ID_ZEMLJE,ug.ID_UGOVORA,
       ug.NAP_UGOVORA,fn.TEKST_NAPOMENE,kat.NAZIV_ELEM,
CASE fakt_lit
    WHEN 'Y' THEN  'L'
    ELSE kat.JM
    END as JM,
npl.OPIS_NACINA_PLACANJA,p.ID_POREZA,

p.OPIS_POREZA,p.PROC_POREZA,p.POREZ_JE_ZA_USLUGU,pp.NAZ_PARTNERA,pp.ULICA_PP,pp.ADR_PP,pr.NAZ_PRIMAOCA,rd1.PRZ_RADNIKA
ASPRZFKT, 
       rd1.IME_RADNIKA AS IMEFKT,rd2.PRZ_RADNIKA AS PRZSEF,rd2.IME_RADNIKA AS IMESEF,fi.ZIRO_RAC,DAT_KP AS
DATUM_IZF,fi.DAT_OTPREME,
       fi.ROK_PLACANJA,(fi.DATUM_IZF+fi.ROK_PLACANJA) AS
ROKDATUM,fi.IZJAVA_BR,fi.DAT_IZJAVE,fi.br_zaklj,fi.br_inof,fi.kurs,fi.NAP_IZF,fi.JE_FAKTURA,fi.OZN_VAL_NBJ_STRAS
ID_VALUTE,
       sfi.RBR_STAVKE_FI,null as AkcizaProc,
skp.KOL_KP as KOL_FI,
coalesce(skp.uk_roba_kp,0) as vrobe,
coalesce(skp.uk_akciza_din_kp,0) as AkcizaDin,
coalesce(skp.uk_man_tr_kp,0) as mantr,
coalesce(skp.uk_marza_kp,0) as marza,
coalesce(pskp.uk_porez,0) as Porez
from FAKTURA_IZLAZNA fi LEFT OUTER JOIN UGOVOR ug
    ON(fi.ID_UGOVORA = ug.ID_UGOVORA)
    LEFT OUTER JOIN Valuta zm
    ON(fi.OZN_VAL_NBJ_STR = zm.OZN_VAL_NBJ_STR)
         --here is modification
        LEFT JOIN NACIN_PLACANJA npl
        ON(fi.ID_NACINA_PLACANJA = npl.ID_NACINA_PLACANJA),

     PRIMAOC pr,
     POSLOVNI_PARTNER pp,

     KORISNIK ko1,
     KORISNIK ko2,
     RADNIK rd1,
     RADNIK rd2,
     STAVKA_FAKTURE_IZLAZNE sfi,
     KATALOG kat,
     KNJIZNO_PISMO kp    LEFT OUTER JOIN FAKTURA_NAPOMENA fn
    ON (kp.ID_NAPOMENA = fn.ID_NAPOMENA),
     STAVKA_KP skp LEFT OUTER JOIN porez_skp pskp
        ON (skp.id_pgodine = pskp.id_pgodine and
        skp.id_oznake_otpreme = pskp.id_oznake_otpreme and
        skp.id_fakture_izlazna = pskp.id_fakture_izlazna and
        skp.id_knj_pisma = pskp.id_knj_pisma and
        skp.rbr_stavke_fi = pskp.rbr_stavke_fi)
        LEFT OUTER JOIN porez p
        ON (pskp.id_poreza = p.id_poreza)
WHERE
    fi.ID_PGODINE = :ID_PGODINE AND
    fi.ID_OZNAKE_OTPREME = :ID_OZNAKE_OTPREME AND
    fi.ID_FAKTURE_IZLAZNA = :ID_FAKTURE_IZLAZNA AND
    fi.ID_PRIMAOCA = pr.ID_PRIMAOCA AND
    fi.ID_PARTNERA = pp.ID_PARTNERA AND
    fi.ID_KORISNIKA = ko1.ID_KORISNIKA AND
    ko1.ID_RADNIKA = rd1.ID_RADNIKA AND
    fi.ID_SEFA = ko2.ID_KORISNIKA AND
    ko2.ID_RADNIKA = rd2.ID_RADNIKA AND
    fi.ID_PGODINE = sfi.ID_PGODINE AND
    fi.ID_OZNAKE_OTPREME = sfi.ID_OZNAKE_OTPREME AND
    fi.ID_FAKTURE_IZLAZNA = sfi.ID_FAKTURE_IZLAZNA AND
    fi.JE_FAKTURA = 'Y' AND
    sfi.ID_ELEMENTA = kat.ID_ELEMENTA AND
    fi.ID_PGODINE = kp.ID_PGODINE AND
    fi.ID_OZNAKE_OTPREME = kp.ID_OZNAKE_OTPREME AND
    fi.ID_FAKTURE_IZLAZNA = kp.ID_FAKTURE_IZLAZNA AND
    kp.ID_KNJ_PISMA = :ID_KNJ_PISMA AND
    kp.ID_KNJ_PISMA = skp.ID_KNJ_PISMA AND
    sfi.ID_PGODINE = skp.ID_PGODINE AND
    sfi.ID_OZNAKE_OTPREME = skp.ID_OZNAKE_OTPREME AND
    sfi.ID_FAKTURE_IZLAZNA = skp.ID_FAKTURE_IZLAZNA AND
    sfi.RBR_STAVKE_FI = skp.RBR_STAVKE_FI
ORDER BY fi.ID_PGODINE,fi.ID_OZNAKE_OTPREME,fi.ID_FAKTURE_IZLAZNA,
        sfi.RBR_STAVKE_FI,
        p.ID_POREZA

both sql work fine on postgres7.4.6
В списке pgsql-bugs по дате отправления:
Предыдущее

От: "Matthew T. O'Connor"
Дата: 11 декабря 2004 г., 20:54:25
Сообщение: Re: pg_autovacuum fails to run as a windows service (beta4)
Следующее

От: Michael Fuhr
Дата: 11 декабря 2004 г., 20:56:30
Сообщение: 8.0.0rc1 core dump with PREPARE in a function
Вход в личный кабинет

Восстановление пароля

Подтверждение аккаунта

Изменение пароля

is it bug

Предыдущее

Следующее
