Re: RHEL repo package crc mismatches

Hello Devrim, You were absolutely right. Resynchronising solved the problem. Now everything is OK again. Thanks for the quick help. Greetings Michael 4. Mai 2023 20:43, "Devrim Gündüz" schrieb: > Hi Michael, > > On Thu, 2023-05-04 at 04:46 +, Brainmue wrote: > >> The problem is fixed

Re: What type of Compiler to SQL? Memory-Image (Load-and-Go) Format?

> On May 4, 2023, at 18:00, Wen Yi wrote: > > Hi team, > I am a newbie to the postgres. > When I am studying the compiler,the text book tell me there is there type of > compiler. > • Assembly Language Format > • Relocatable Binary Format > • Memory-Image (Load-and-Go) Format

Re: What type of Compiler to SQL? Memory-Image (Load-and-Go) Format?

On Thu, May 4, 2023 at 6:00 PM Wen Yi wrote: > Hi team, > I am a newbie to the postgres. > When I am studying the compiler,the text book tell me there is there type > of compiler. > >1. Assembly Language Format >2. Relocatable Binary Format >3. Memory-Image (Load-and-Go) Format > > >

Re: What type of Compiler to SQL? Memory-Image (Load-and-Go) Format?

On Thu, May 4, 2023 at 09:16:20PM -0400, Bruce Momjian wrote: > Lex and yacc load command-specific structures, or a Query structure for > SELECT, INSERT, UPDATE, DELETE, MERGE. > > The Query structure is converted into a Plan which is executed by the > executor. It is not compiled into assembly

Re: What type of Compiler to SQL? Memory-Image (Load-and-Go) Format?

On Fri, May 5, 2023 at 01:00:37AM +, Wen Yi wrote: > Hi team, > I am a newbie to the postgres. > When I am studying the compiler,the text book tell me there is there type of > compiler. > > 1. Assembly Language Format > 2. Relocatable Binary Format > 3. Memory-Image (Load-and-Go) Format >

What type of Compiler to SQL? Memory-Image (Load-and-Go) Format?

Hi team, I am a newbie to the postgres. When I am studying the compiler,the text book tell me there is there type of compiler. 1. Assembly Language Format 2. Relocatable Binary Format 3. Memory-Image (Load-and-Go) Format I check the postgres's sql compiler, and it's achieved by lex & ya

Re: "PANIC: could not open critical system index 2662" - twice

On Fri, May 5, 2023 at 11:15 AM Thomas Munro wrote: > What does select > pg_relation_filepath('pg_class_oid_index') show in the corrupted > database, base/5/2662 or something else? Oh, you can't get that far, but perhaps you could share the pg_filenode.map file? Or alternatively strace -f Postgr

Re: "PANIC: could not open critical system index 2662" - twice

On Fri, May 5, 2023 at 11:15 AM Thomas Munro wrote: > Now *that* is a piece of > logic that changed in PostgreSQL 15. It changed from sector-based > atomicity assumptions to a directory entry swizzling trick, in commit > d8cd0c6c95c0120168df93aae095df4e0682a08a. Hmm. I spoke too soon, that only

Re: "PANIC: could not open critical system index 2662" - twice

On Fri, May 5, 2023 at 6:11 AM Evgeny Morozov wrote: > Meanwhile, what do I do with the existing server, though? Just try to > drop the problematic DBs again manually? That earlier link to a FreeBSD thread is surely about bleeding edge new ZFS stuff that was briefly broken then fixed, being disco

Re: RHEL repo package crc mismatches

Hi Michael, On Thu, 2023-05-04 at 04:46 +, Brainmue wrote: > The problem is fixed in most of the repositories I synchronise, but in > one I now have a new one. With the package: postgresql13-odbc- > 13.00.-1PGDG.rhel7.x86_64.rpm > > For the pgdg13 RHEL 7 repository: > > [MIRROR] postgres

Re: "PANIC: could not open critical system index 2662" - twice

On 5/4/23 13:10, Evgeny Morozov wrote: [snip] I'm now thinking of setting up a dedicated AWS EC2 instance just for these little DBs that get created by our automated tests. If the problem happens there as well then that would strongly point towards a bug in PostgreSQL, wouldn't it? Many other p

Re: "PANIC: could not open critical system index 2662" - twice

On 4/05/2023 6:42 pm, Laurenz Albe wrote: > On Thu, 2023-05-04 at 15:49 +, Evgeny Morozov wrote: >> Well, the problem happened again! Kind of... This time PG has not >> crashed with the PANIC error in the subject, but pg_dumping certain DBs >> again fails with >> >> >> pg_dump: error: connectio

Re: "PANIC: could not open critical system index 2662" - twice

On Thu, 2023-05-04 at 15:49 +, Evgeny Morozov wrote: > Well, the problem happened again! Kind of... This time PG has not > crashed with the PANIC error in the subject, but pg_dumping certain DBs > again fails with > > > pg_dump: error: connection to server on socket > "/var/run/postgresql/.s.

Re: "PANIC: could not open critical system index 2662" - twice

On 14/04/2023 10:42 am, Alban Hertroys wrote: > Your problem coincides with a thread at freebsd-current with very > similar data corruption after a recent OpenZFS import: blocks of all > zeroes, but also missing files. So, perhaps these problems are related? > Apparently, there was a recent fix for

Re: Invoking SQL function while doing CREATE OR REPLACE on it

Thanks for the insight, Erik. Turns out, it was indeed liquibase which was: - dropping the functions in one transaction (inadvertently as the result of a DROP TYPE CASCADE) - immediately followed by the next transaction which did a CREATE OR REPLACE FUNCTION which recreated these functions The t

Re: Trigger questions

On Thu, May 4, 2023 at 7:04 AM Justin wrote: > > > On Thu, May 4, 2023 at 9:49 AM DAVID ROTH wrote: > >> 1) Can I create a trigger on a view? >> 2) Do triggers cascade? >> >> Say I have an insert trigger on a table. >> And, I have an insert trigger on a view that references this table >> If I do

Re: Trigger questions

On 5/4/23 07:03, Justin wrote: On Thu, May 4, 2023 at 9:49 AM DAVID ROTH > wrote: __ 1) Can I create a trigger on a view? 2) Do triggers cascade? Say I have an insert trigger on a table. And, I have an insert trigger on a view that references

Re: Trigger questions

On Thu, May 4, 2023 at 9:49 AM DAVID ROTH wrote: > 1) Can I create a trigger on a view? > 2) Do triggers cascade? > > Say I have an insert trigger on a table. > And, I have an insert trigger on a view that references this table > If I do an insert on the view, will both triggers fire? > Can not

Trigger questions

1) Can I create a trigger on a view? 2) Do triggers cascade? Say I have an insert trigger on a table. And, I have an insert trigger on a view that references this table If I do an insert on the view, will both triggers fire?

Re: The logfile stop upgrade after a vim write

> On 04/05/2023 11:54 CEST lz ma wrote: > > 1. pg_ctl -D data -l MyLog > 2. vim MyLog : add some words, save and exit > 3. after vim operation, MyLog will never upgrade except restart server > I know it caused by file descripter only open once at the start by postgres, > and vim operation rename t

The logfile stop upgrade after a vim write

1. pg_ctl -D data -l MyLog 2. vim MyLog : add some words, save and exit 3. after vim operation, MyLog will never upgrade except restart server I know it caused by file descripter only open once at the start by postgres, and vim operation rename the file to MyLog~, so postgres can't up