mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-08-24 13:27:19 +02:00
a28f117790
days. It seems to be a FAQ, and I think I know why. When creating a 'c' language function, CREATE FUNCTION is fed the shared object filename, and seems to succeed. Only when trying to use the function is an error thrown, by which time the coder thinks something's wrong with executing the code, not with loading it. I think I once saw it proposed to load shared objects at function creation time, but that idea was shot down on the grounds of resident memory bloat, ISTR. Here's a patch for a compromise: all it does is stat() the file, just like the loader code does, so that the errors caused by non existent files, and no directory 'x' permissions (the most common ones, it seems), get caught while the developer is still thinking about code loading. It doesn't catch all errors (like the code not being readable by the postgres user) but seems to catch the most common, without actually opening the file. What do you think? Ross |
||
|---|---|---|
| .. | ||
| _deadcode | ||
| async.c | ||
| cluster.c | ||
| command.c | ||
| comment.c | ||
| copy.c | ||
| creatinh.c | ||
| dbcommands.c | ||
| define.c | ||
| explain.c | ||
| indexcmds.c | ||
| Makefile | ||
| proclang.c | ||
| remove.c | ||
| rename.c | ||
| sequence.c | ||
| trigger.c | ||
| user.c | ||
| vacuum.c | ||
| variable.c | ||
| view.c | ||