enied for table outbox_event
You need SELECT privilege too in order to read the "id" column.
regards, tom lane
an OSSLCipher involves only free() operations
and no other resources). I think the only real win we'd get from
such a layer is that OpenSSL's allocations would be better exposed
for accounting purposes, eg the pg_backend_memory_contexts view.
That's not negligible, but I don't find it a compelling reason to
do the work, either.
regards, tom lane
on "returns table(id int)"
of the function, which has no associated table.
regards, tom lane
believed that and not rechecked the length while
storing into the matview. Not sure if this behavior change was
intentional or an accidental product of refactoring.
regards, tom lane
Atul Kumar writes:
> I checked the permissions on /tmp directory and it shows "drwxrwxrwt."
> already, do I need to check something else as well ?
That seems fine, but what about the socket file itself?
regards, tom lane
own could be to remove or increase all the
varchar limits in the matview declaration, load the data, and then
probe for bad entries with something like "select * from matview where
length(some_varchar_field) > 255".
regards, tom lane
socket does not
> exist?
Nope, that should mean either that /tmp is not readable, or that the
socket file is there but has restrictive permissions.
That doesn't necessarily make Adrian's answer wrong though.
regards, tom lane
t8_tbl (cost=0.00..1.05 rows=5 width=16)
NOTICE:-> Hash (cost=1.05..1.05 rows=5 width=4)
NOTICE: -> Seq Scan on int4_tbl (cost=0.00..1.05 rows=5 width=4)
DO
regards, tom lane
Indeed. In theory, if you use --enable-depend, you needn't do
"make clean". But I don't trust that a whole lot personally.
I find that using ccache gets most of the win with fewer assumptions.
regards, tom lane
should have included that in LIBS if you specified
--with-openssl, but maybe it failed to. Can you check the
configured value of LIBS (in src/Makefile.global) to see?
If it's not there, it would be useful to see the contents of
the config.log log file.
regards, tom lane
erator pseudo-constant
which this isn't, nor does << have a negator operator that could
allow the NOT to be simplified out.
Wouldn't
drange && daterange(CURRENT_DATE, NULL, '[)')
serve the purpose? That should be indexable.
regards, tom lane
lanced they are? (Assume PG12+.)
As far as I know, we don't have a problem of that sort. Continued
insertions will eventually force a split of the root node, which will
rebalance the tree.
regards, tom lane
e could print "(ALL t.a >= $0 FROM SubPlan 1)".
Some of the other SubLinkTypes might be harder to represent
in a way that makes sense to users.
I made a quick-hack patch to play with, if you're interested.
regards, tom lane
diff --git a/src/backe
Jim Vanns writes:
> I should have already stated I did begin with EXPLAIN but given they
> don't easily work with (the internals) stored/procedures, it wasn't
> useful in this case.
auto_explain with nested statements enabled might help?
regards, tom lane
ugh, which might matter for such a low-level failure
as this.
regards, tom lane
Dominique Devienne writes:
> On Tue, Jan 16, 2024 at 10:59 PM Tom Lane wrote:
>> The problem is that now you have a switch somewhere (whether a GUC
>> or something else, still a switch) that fundamentally changes the
>> transactional semantics seen by applications. Run an
it executes to
>> confirm my suspicion - does anyone have any tips on that?
> Explain:
> https://www.postgresql.org/docs/current/sql-explain.html
Specifically, if EXPLAIN ANALYZE shows a lot of time spent in the
enforcement trigger for the FK, this is likely what's happening.
regards, tom lane
re would be even more broken client code.
regards, tom lane
er HashAgg
step won't really care. See use_physical_tlist() in createplan.c.
What I'm confused about is why 9.4 didn't do the same.
That optimization heuristic is very old, and certainly
would be applied by 9.4 in some circumstances. Testing
says the behavior in this specific case changed at 9.6.
I'm not quite interested enough to drill down further...
regards, tom lane
lk about what additional stuff might be
needed in that infrastructure to make it work for a COBOL wrapper
... but I think somebody else has to take point on making that
happen.
regards, tom lane
s, there
is savings -- we simply don't store anything for a null column).
There's more detail at
https://www.postgresql.org/docs/current/storage-page-layout.html
regards, tom lane
desire to use these
format fields. As noted upthread, SET LOCAL together with a (dummy)
"SET timezone" clause in the function definition can be used to get
the effect of a function-local setting of the parameter. I don't
know of another way to achieve that result above the C-code level.
regards, tom lane
Did you get any warnings during build?
regards, tom lane
umn. Check again.
I am guessing that the OP tried to put a literal NUL character
into the COPY data. A bytea value in COPY data needs to be
text-encoded as per one of the alternatives explained in the
manual. Alternatively, you could jump through the hoops involved
in sending binary COPY data.
regards, tom lane
So that seems like an
oversight.
regards, tom lane
ve not looked at the code though.
regards, tom lane
umber and re-compile, or would that break other
> things?
A bit of "git blame" archaeology says that that traces back to
commit bf7737a938827608ce79586efe55c642c1a4a7d3
Author: Tom Lane
Date: Wed Jan 26 21:55:26 2005 +
On Windows, set the postmaster executable's sta
regards, tom lane
over
the other.
regards, tom lane
al fix, perhaps a newer version of LLVM is needed?
I don't see a problem testing this query on my RPI with Ubuntu 23.10
(LLVM 16).
regards, tom lane
ether it'd really
make sense to have an exception for that.
regards, tom lane
"Peter J. Holzer" writes:
> On 2023-12-22 10:31:14 -0500, Tom Lane wrote:
>> Binaek Sarkar writes:
>>> Interestingly, the *build completes successfully when the .a file is
>>> smaller* (around 100 MB).
>> Pure luck I suspect.
> I seem to remember
ed libraries, not .a files.
> Interestingly, the *build completes successfully when the .a file is
> smaller* (around 100 MB).
Pure luck I suspect.
regards, tom lane
ion about the stuck session(s).
> Here is a stack trace from gdb for one of the frozen sessions:
This appears to be a trace of a psql process waiting for a query
result. It won't teach you much about what the server is doing.
regards, tom lane
that'd work considerably
further back. Or you could make a custom C function that
leverages pg_strong_random().
regards, tom lane
e maintainer-clean"?
If that doesn't fix it, please build with --enable-debug so that you
can get a more detailed stack trace.
regards, tom lane
k this
way rather than using shared libraries.
regards, tom lane
symbol: pg_vsnprintf
libpgcommon and libpgport
regards, tom lane
uot;` ;;
which seems identical to what you reported. So that takes some
steam out of the idea that the file was generated incorrectly
in your build, pointing more to the idea that your shell is not
reading it as-expected.
regards, tom lane
t GNU sed?
I'm also wondering if the shell in use is nonstandard. The configure
script would likely already have failed if you tried to run it with,
say, csh; but maybe more-subtly-incompatible shells could give rise
to this symptom.
regards, tom lane
gger on the remote side is currently the best
way around that for cases where you can't set up a suitable
default on the local table.
regards, tom lane
;d just lead to thrashing/bloat in the pg_namespace catalog,
since they'd be needed again eventually.
regards, tom lane
> Thanks,
> Vishu
postgresql.git&a=commitdiff&h=ce0fdbfe972
regards, tom lane
the execution time is increased
> significantly.
... so, indeed, the planner was correct to use a seqscan.
> Not expecting this behavior currently.
Your expectation is faulty.
regards, tom lane
likely a Citus-specific
issue, and that you came to the wrong place for expertise on that.
regards, tom lane
ut maybe not with older ones.
regards, tom lane
John DeSoi writes:
>> On Nov 30, 2023, at 7:53 PM, Tom Lane wrote:
>> Ugh, not only Heimdal but a very obsolete version thereof? It borders
>> on negligence for the homebrew PG package to be building against that.
>> They should be pulling in homebrew's MIT Kerbe
John DeSoi writes:
> On Nov 30, 2023, at 2:07 PM, Tom Lane wrote:
>> What troubles me about that stack trace is the references to Heimdal.
>> We gave up supporting Heimdal (and v16 explicitly rejects building
>> with it) because its support for Kerberos credentials was
ky. So I'm inclined to guess that you are running
into some Heimdal bug. Try to rebuild libpq using MIT Kerberos
and see if things get better.
regards, tom lane
uch of the advice you got here
is relevant to it.
regards, tom lane
it'd have
gone for an indexscan, I'm pretty sure.
Are your ANALYZE stats up to date on this table? If so, there must
be some strong correlation between the payload and expiration
conditions that the planner doesn't know about. Perhaps creating
extended statistics on those two columns would help.
regards, tom lane
Don Seiler writes:
> On Mon, Nov 27, 2023 at 6:02 PM Tom Lane wrote:
>> Is OpenSSL in use? If so, what version? I'm wondering if this is a
>> variant of the OpenSSL 3.2.0 compatibility problem we just heard of:
> My colleague does confirm it is OpenSSL 3.2.0:
> =
DDYsYaL7mv%2BoSLUij2h_u6hvD4Qmv-7PK7jkji0uyQ%40mail.gmail.com
regards, tom lane
. But some distros consider that insecure so they
override it, typically to /var/run/postgresql/.)
The easiest workaround if you have a mishmash of Postgres libraries
is to tell the postmaster to create sockets in both places.
See "unix_socket_directories" parameter.
regards, tom lane
ne, so how will you know where the row boundaries are?
That is, is a newline a row separator or part of the data?
You can debate the intelligence of any particular quoting/escaping
scheme, but imagining that you can get away without having one at
all will just create its own problems.
7;y', 'z', 't']::varchar[] <@ ss.arr) IS NOT TRUE
but I don't think that's more readable really, and it will save little.
In either case, this would result in computing array_agg once for
each group of test_id values in "stuffs", while your original computes
a similar aggregate for each row in "test". So whether this is better
depends on the relative sizes of the tables, although my proposal
avoids random access to "stuffs" so it will have some advantage.
regards, tom lane
ELSE
RETURN QUERY query-without-decryption;
END IF;
which seems a good deal safer than relying on undocumented details
of planner optimization behavior.
I also wonder why you don't make crypto_secretbox_open a bit
more robust --- at the very least mark it strict (RETURNS NULL
ON NULL INPUT).
regards, tom lane
ache_mode setting might provide a
workaround.
regards, tom lane
se.
So I was skeptical that the details presented were even correct.
I think whatever is causing the behavioral change is something else
that the OP hasn't identified/controlled for. Hard to tell with
such fragmentary details.
regards, tom lane
"David G. Johnston" writes:
> On Thursday, November 23, 2023, Tom Lane wrote:
>> This question is unanswerable as given. You have not even defined
>> what you mean by "fail" (error? wrong query result?), let alone
>> provided enough detail for someone
e the problem.
regards, tom lane
be made for the catalog
changes, but usually the bulk of the WAL for a pg_restore run comes
from loading data, and this recipe eliminates that. (Of course,
you cannot use it on a replication primary.)
regards, tom lane
ress this. You should probably look
harder at the idea that you have some configuration problem that's
triggering your WAL bloat. If COPY can run you out of WAL space,
then so could any future bulk insert or update.
regards, tom lane
e pg_repack
developers? (Maybe they read pgsql-general, but I wouldn't count
on it.)
regards, tom lane
t
skips right to the non-SSL attempt.
Laurenz's suggestion of adding sslmode=require is a good debugging
step either way, since it will either tell you for sure that you
are missing SSL support or show you the failure from the single
SSL-enabled attempt. Alternatively, turn on log_connections
02 rows. The right node 3. How can this result in >1e9 rows?
The rowcount estimate for the join is not derived by multiplying the
rowcount estimates of the two inputs. Having said that, this looks
pretty inconsistent. Can you show a test case that acts like that?
regards, tom lane
> I would say it has to do with what '...' is doing?
We'd need to see a complete example to do more than speculate.
The planner definitely does skip unreferenced SELECT CTEs, though.
regards, tom lane
omebrew, maybe that's out of date?
Try removing the associated directories from your PATH to see
if it works better.
* It doesn't look like you're using ccache, but if you are,
flushing its cache might not be a bad idea.
regards, tom lane
lity of the CTE
names across all the CTEs in the WITH.
regards, tom lane
ctly zero context that would help
anyone else in understanding or duplicating the problem.
"It doesn't work on macOS 14.1.1" is not useful, because that
works fine for me and a number of other people.
regards, tom lane
lly valid SQL, but they don't ever reach parse analysis
so nothing happens beyond minimal syntax checking.
If that's not enough, what you'll want to look at is using EXECUTE
to execute dynamically-constructed SQL.
regards, tom lane
nt/sql-expressions.html#SYNTAX-AGGREGATES
Thank the SQL spec for that weirdness.
regards, tom lane
e. You should start by trying
to identify what component is actually throwing that error.
regards, tom lane
and
new style, which doesn't seem like a good thing.
(The verification done by check_function_bodies likewise can't
work if earlier statements make DDL changes that affect later
ones.)
As per the advice in the fine manual, use plpgsql for this
sort of task.
regards, tom lane
ileges on the tables
* Role foo_dba is granted foo_owner but not DML privileges.
This is, of course, trivially breakable by any foo_dba who
doesn't want to play by the rules, but as long as you log
DDL there will at least be log traces that she did so.
regards, tom lane
though.
A less difficult answer would be to write a function that breaks up
the input into (say) an array of text and then use the existing
GIN array support. But you'd pay for that by needing to write more
complicated queries to use the index.
regards, tom lane
regards, tom lane
ng the ActivePortal might help (see
function_parse_error_transpose, which I think is the only in-core user).
> 2. column attribute (specifically the TYPMOD) for the affected column
No. How would you even define "affected column"?
regards, tom lane
to recast an EXCEPT query as an
antijoin.
regards, tom lane
> connection from host "remote_ip", user "postgres", SSL off
... and that is complaining about the lack of an entry for
replication connections. They are handled by different pg_hba.conf
entries.
regards, tom lane
for PG. Perhaps
someone will take an interest in implementing this feature, or
perhaps not. But there's no project-wide goal to make it happen,
much less a timetable. Even if someone does take an interest,
they might not succeed in producing a committable patch.
regards, tom lane
rrency
with foreign-key checks that might wish to grab a read-only (shared)
lock on such a tuple.
A DELETE, or an UPDATE that is modifying key columns, has to
conflict with foreign-key checks.
regards, tom lane
ssion of \e seems to me to cover this.
If you want to suggest some adjustments to make it clearer, we
could discuss that.
regards, tom lane
Albrecht =?iso-8859-1?b?RHJl3w==?= writes:
> - How would a “mood” parameter be encoded when it is passed to the function?
It's an OID, which you'd have to look up in the pg_enum catalog if
you want to know the string representation.
regards, tom lane
it's
not going anywhere either.
You should certainly make the point that if your problem looks like
partitioning, you should use partitioning rather than some hand-rolled
use of plain inheritance. But there are valid use-cases where you
actually do want more columns in the child tables than the parent.
regards, tom lane
I guess. We don't mark anything trusted
if it can be used to cause outside-the-database effects; and in this
case the ability to connect to other databases qualifies as that.
regards, tom lane
307906 4b2c2 libpq.so.5.14
It seems likely that there's some oddity in your build environment.
Maybe the libssl.so and libcrypto.so symlinks aren't present? Or take
a close look at the command that links libpq.so, and see if any odd
switches have crept in.
regards, tom lane
loat output algorithm, eg here:
https://github.com/ulfjack/ryu
regards, tom lane
es should have been enough to fix it.
See
https://wiki.postgresql.org/wiki/Locale_data_changes
regards, tom lane
likely to hold still for long) it's pretty hard
to say exactly how many PROCLOCK entries you might need. And
bloating the lock table size by max_connections/2 or so to try
to brute-force that doesn't seem like a good plan.
I'd just raise max_prepared_transactions until you stop seeing
problems, and then maybe add a factor of two safety margin.
regards, tom lane
straints, which is what I think you're looking for here.
If somebody came with a well-thought-out patch to add that feature,
we'd likely take it. But this is definitely a "scratch your own
itch" situation; I don't know of anyone already working on such
a thing.
regards, tom lane
plans for the two cases. PG does
not have the sort of run-time plan choice mechanism that you're
describing for Oracle.
regards, tom lane
hole though, the entire question seems like solving the wrong
problem. If you have to resort to this kind of thing to get your
answers, it's past time to rethink your data representation.
regards, tom lane
slashes in
the default format. You could use CSV format, perhaps, but that
has its own quoting rules that also mean that what comes out is
not going to be json-and-nothing-but. See "File Formats" here:
https://www.postgresql.org/docs/current/sql-copy.html
regards, tom lane
eges for the user in all databases in the cluster using one view,
> select.
This is not possible, because a session can only see the catalogs for its
own database (plus the shared catalogs, but those only describe shared
objects).
regards, tom lane
t follow its basic control flow. Indent
according to the brace structure, and your life will get easier.
regards, tom lane
r helpful info at
https://wiki.postgresql.org/wiki/Corruption
regards, tom lane
duce, not increase, the set of strings we'll call identifiers.
regards, tom lane
his is difficult to do without breaking
mountains of backend code, but there's been some discussions about
ways to accomplish that. The most recent thread I could find is
https://www.postgresql.org/message-id/flat/CALSd-crdmj9PGdvdioU%3Da5W7P%3DTgNmEB2QP9wiF6DTUbBuMXrQ%40mail.gmail.com
regards, tom lane
ke the extra log entries, there's a command-line
switch that forces psql to prompt for password before connecting
the first time. Of course, that might result in prompting for
a password that's not really needed.
regards, tom lane
201 - 300 of 1912 matches
Mail list logo
