Re: ERROR: bogus varno: 2
От | Erison Gmail |
---|---|
Тема | Re: ERROR: bogus varno: 2 |
Дата | |
Msg-id | 0e723e6b-4bcd-f704-71cc-b78fb9fb015f@gmail.com обсуждение исходный текст |
Ответ на | Re: ERROR: bogus varno: 2 (Murtuza Zabuawala <murtuza.zabuawala@enterprisedb.com>) |
Список | pgadmin-support |
Thank you for your help
I'm waiting, to test.
hugs
available
ATT. Erison Roberto Belon Técnólogo em processamento de dados Bacharel em desenvolvimento de software para web email: nosire@gmail.com skype: nosireerb ICQ: 609535756 Fone: 55(17)99714-9152 (vivo)(Whatsapp) 55(17)98211-0279 (Tim)
Em 02/04/2019 00:31, Murtuza Zabuawala escreveu:
Hi,This issue(RM#3995) has been fixed, It will be available in the next release which is pgAdmin4 v4.4.On Tue, 2 Apr 2019, 05:12 Erison Gmail, <nosire@gmail.com> wrote:Good night friends
This is my first message, thank you in advance.
I have some databases that I migrated from postgresql 9.5 to 10, and in
some tables when trying to view SQL I get the following error: "ERROR:
bogus varno: 2"
After some queries I came to the conclusion that the error appears when
I have in the table a trigger that has AFTER UPDATE condition.
Example:
"AFTER UPDATE OF notan1 ON public.nota FOR EACH ROW WHEN ((old.notan1 IS
DISTINCT FROM new.notan1))"
I already ran backup of the database, and I removed the trigger, and
circled the CREATE of it again and the sql normal wheel, the triggers
are working.
Thank you.
--
ATT.
Erison Roberto Belon
Técnólogo em processamento de dados
Bacharel em desenvolvimento de software para web
email: nosire@gmail.com
skype: nosireerb
ICQ: 609535756
Fone: 55(17)99714-9152 (vivo)(Whatsapp)
55(17)98211-0279 (Tim)
В списке pgadmin-support по дате отправления: