On Mon, Feb 3, 2025 at 3:17 PM Tom Lane wrote:
> Just to catch programming errors, ie passing the wrong pointer
> value to some SPI function. See the checks for it in spi.c.
Aha! Perfect, I thought it was something like that. Thank you!
Marcelo.
Hi
po 3. 2. 2025 v 0:06 odesílatel Marcelo Fernandes
napsal:
> Hi there,
>
> I have been trying to debug what queries an extension is firing. After
> reading
> the code for the extension, I noticed that all the statements are fired
> via the
> SPI interface, most specifically, using the SPI_exec
Marcelo Fernandes writes:
> Reading through the SPI code I see this definition:
> #define _SPI_PLAN_MAGIC 569278163
> What is its purpose?
Just to catch programming errors, ie passing the wrong pointer
value to some SPI function. See the checks for it in spi.c.
regards
Hi there,
Reading through the SPI code I see this definition:
#define _SPI_PLAN_MAGIC 569278163
Which is used in he _SPI_plan struct in src/include/executor/spi_priv.h:
typedef struct _SPI_plan
{
int magic;
...
}
What is its purpose?
Thank you.
Marcelo
Hi there,
I have been trying to debug what queries an extension is firing. After reading
the code for the extension, I noticed that all the statements are fired via the
SPI interface, most specifically, using the SPI_execute* family of functions.
However, the problem is that these statements don'
On 2025-02-02 12:12:07 +, Paul Brindusa wrote:
> I had the exact same query as Junwang proposed.
Assuming that by "query" you mean the crontab entry:
Well, if if was *exactly* the same it's unlikely to work since you
probably don't have a directory literally called "/path/to/logs". If you
mad
Hi,
For automation purposes, I'd like to identify an idempotent pair of command
sequences such that I can CREATE SUBSCRIPTION and DROP SUBSCRIPTION without
knowing whether a previous attempt to do either operation partly succeeded
or not. Specifically, as per Google and the notes in the docs (
http
On 2025-01-28 13:40:42 +, Paul Brindusa wrote:
> @Junwang apologies, I should have mentioned that we've tried setting up a
> crontab and it has not worked.
Then you have a cron problem and not a postgresql problem.
What that problem is is impossible to say with the information you have
given
