You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
The reason this wasn't supported before was that GiST indexes need anincreasing sequence to detect concurrent page-splits. In a regular WAL-logged GiST index, the LSN of the page-split record is used for thatpurpose, and in a temporary index, we can get away with a backend-localcounter. Neither of those methods works for an unlogged relation.To provide such an increasing sequence of numbers, create a "fake LSN"counter that is saved and restored across shutdowns. On recovery, unloggedrelations are blown away, so the counter doesn't need to survive thateither.Jeevan Chalke, based on discussions with Robert Haas, Tom Lane and me.