which will be applied to connections to the Postgres
server, nothing else.
regards, tom lane
migration
is to use the newer release's pg_dump to suck the data out of
the older server. If you can't do that, it'll (probably)
still work, but you may have cosmetic issues like this one.
regards, tom lane
problem? Set a breakpoint at errfinish, run the CREATE
EXTENSION, and when it stops send us the output of "bt".
(Make sure that fmgr_info_cxt_security appears one or two levels
down in the trace, else you stopped at the wrong message output.)
https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
regards, tom lane
k the exact details here, but I believe you can find
related examples in our regression tests) and then store the function's
result into a table.
regards, tom lane
tly this
is laziness or lack of round tuits, but in some cases there are
also interesting semantic problems.
regards, tom lane
n production. I'd expect though that
you could apply it with ALTER USER SET.
regards, tom lane
Jeremy Finzel writes:
> On Mon, Apr 22, 2019 at 3:47 PM Tom Lane wrote:
>> Sure sounds to me like what you are setting is something client-side,
>> not the server's log verbosity. It works for me:
> I am running it differently - explicitly raising a LOG level message, no
... and that's where it's coming from. Seems like you have corrupt
data in pg_language. Might be entertaining to see what
"select * from pg_language" gives.
regards, tom lane
y setting
lanvalidator back to its correct value (2247) but it'd be
wise to first inquire as to how it got like this.
regards, tom lane
herry-pick "security"
patches doesn't understand the realities of database work.
regards, tom lane
ider using arrays,
or perhaps composite sub-structures (JSON maybe?).
regards, tom lane
anner's default behavior in the absence of any
stats, you could omit the post-insertion ANALYZE in this case. But
I'm not sure that that would represent a test that has much to do with
production situations.
regards, tom lane
on I am asking is that e.g. int4[] and _int4 behave differently.
> Although they look the same, the have different pg_attribute.attndims.
Yeah. Nothing really cares about attndims though ... it's vestigial.
Perhaps we should remove it someday.
regards, tom lane
Even if we wanted to put work into a column that's so vestigial that
taking it out is a reasonable proposal, we would certainly never
back-patch such a change; nor would existing catalog entries change
even if we did. So you pretty much have to deal with the facts on
the ground, which are that attndims is largely useless.
regards, tom lane
ession=# insert into foo values(array[array[4]::intarray]);
INSERT 0 1
But as this example shows, it's not exactly a transparent solution.
It might be possible to make this specific case work better, but
I think you'd inevitably end up needing lots of explicit casts.
regards, tom lane
ssion behavior,
but it suggests that maybe the client isn't bothering to close the session
cleanly either. The RST rather than FIN would then likely be caused by
SSL having to do an unclean shutdown.
regards, tom lane
=?utf-8?Q?J=C4=81nis_P=C5=ABris?= writes:
> This is only reproducible with SSL connection.
Seems like you might get more insight from OpenSSL experts, then.
(No idea where you find some, but they must exist.)
regards, tom lane
ave a --jobs option, since 9.5 or so. What it does
is to run the dump and restore tasks for different databases of the
cluster in parallel. So it won't help much if you've just got one
DB with a lotta objects, but I thought it was worth mentioning.
regards, tom lane
sing you're hitting some O(N^2) behavior somewhere, and it
might be something we fixed.
Likewise make sure that pg_dump is the newest available in the destination
release series.
regards, tom lane
e worth the time
> if there aren't additional requirements prior to starting the upgrade.
That was my reasoning. It might not help, but it's a simple thing
to do and it might help.
regards, tom lane
, maybe you should cast
or truncate the timestamp down to date.
regards, tom lane
at sort of selectivity estimator have you got attached to that custom
operator?
regards, tom lane
Sergey Koposov writes:
> On Thu, 2019-05-02 at 00:36 -0400, Tom Lane wrote:
>> What sort of selectivity estimator have you got attached to that custom
>> operator?
> This is the code, but basically it is just a constant based on the search
> radius (which is the leftmost
he pgAdmin lists,
eg pgadmin-supp...@lists.postgresql.org
regards, tom lane
ers correspond
to the IEEE spec.
regards, tom lane
[1] https://tools.ietf.org/html/rfc7159#page-6
to show where in the code it's
stuck?
https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
regards, tom lane
etween. Are you using
either SSL or GSS?
regards, tom lane
field is in shared memory. The easiest way to get it reset
would be to restart the postmaster. It's possible you could do it
without that, by starting enough sessions so that one of them takes
up the broken pg_stat_activity slot.
regards, tom lane
there'll be a pretty obvious
failure rather than a lot of stuck readers.
regards, tom lane
segments
with no possible way to throw an error while changecount is odd.
Then somebody abused the heck out of that ...
regards, tom lane
;re worried about
corner cases where we did mess that up, what of corner cases where process
exit fails before getting here? I think the right answer is to bring the
hammer down as soon as we mess up, which is what the critical-section
mechanism is for.
regards, tom lane
could spend endless
amounts of time hypothesizing different kinds of corruption and
endless amounts of code/cycles trying to work around it. But the
right answer is to fix it on the writing side.
regards, tom lane
there
by DDL activity). That requires exclusive lock on pg_attribute,
which would propagate down to the standby.
regards, tom lane
oked at how much adjustment
it'll need for the back branches, but I'm sure there's some.
regards, tom lane
diff --git a/src/backend/postmaster/pgstat.c b/src/backend/postmaster/pgstat.c
index 64986b1..25a1bd9 100644
--- a/src/backend/postmaster/pgstat.c
+++
hs using
different estimators, and since this is all very approximate and
full of heuristic guesses, sometimes they don't match very well.
regards, tom lane
.org/gitweb/?p=postgresql.git;a=commitdiff;h=c3d113136bbaa86fbf1edde7aaf70ba06a6166b7
regards, tom lane
you're very
likely to have inconsistent data.
regards, tom lane
do the catalog corruption that is causing the WAL replay crash.
I hope you have a recent backup to restore from.
regards, tom lane
Alvaro Herrera writes:
> On 2019-May-17, Tom Lane wrote:
>> The good news is that the underlying ALTER TABLE bug is fixed in 11.3.
>> The bad news is that your database is probably toast anyway --- an update
>> won't undo the catalog corruption that is causing the WAL r
ck the whole posting tree before
delete any page. However, we keep another useful change by 218f51584d5: the
tree is locked only if there are pages to be deleted.
regards, tom lane
Will Hartung writes:
>> On May 18, 2019, at 11:02 AM, Tom Lane wrote:
>> In addition to the questions about what PG version you're using, is
>> the backend process that's doing the load actually consuming CPU time,
>> or is it just sitting?
> It’s consuming
on_tables(P.pubname)
+ WHERE C.oid = pg_get_publication_tables.relid;
regards, tom lane
#x27;s unlikely
that the problem depends on the *exact* data you've got --- though it
might depend on string lengths and the number/locations of duplicates.
But you should be able to substitute random strings for the original
values while preserving that.
regards, tom lane
ew. (You can use the Tom's suggestion using LATERAL)
It's a view, not a table, so I don't think you need
allow_system_table_mods. A quick test here says that being
superuser is enough to do a CREATE OR REPLACE VIEW on it.
regards, tom lane
=?UTF-8?Q?Fabr=C3=ADzio_de_Royes_Mello?= writes:
> Em ter, 21 de mai de 2019 às 14:41, Tom Lane escreveu:
>> It's a view, not a table, so I don't think you need
>> allow_system_table_mods. A quick test here says that being
>> superuser is enough to do
lating rows to be inserted in different partitions.
Concurrent development conflict in eb7ed3f30634 and 8224de4f42cc.
Reported-by: Justin Pryzby
Discussion: https://postgr.es/m/20190109065109.ga4...@telsasoft.com
regards, tom lane
r might not see those changes.
regards, tom lane
Ron writes:
> On 5/29/19 8:26 AM, Tom Lane wrote:
>> This doesn't explicitly talk about triggers, but I think our attitude
>> about the case you're discussing is that the results are unspecified.
>> If a trigger fired in one WITH arm tries to look at the table(s)
e larger point here is that right now btree_gin is just a quick
hack, and it seems like it might be worth putting some more effort into
it, because the addition of duplicate-compression changes the calculus
for whether it's useful.
regards, tom lane
s (re-ANALYZE) after the upgrade?
pg_upgrade makes a script for that, but I don't believe it runs it for
you.
regards, tom lane
e systemd's other options for figuring out the
service state work substantially less well.
regards, tom lane
patch right now would be a good deal
smaller than that one, though ;-))
regards, tom lane
er reviewing
https://www.postgresql.org/docs/10/install-procedure.html
to see what other things might make sense to turn on.
regards, tom lane
e system
catalogs along with user tables, but missing out user indexes seems
like a pretty big gap.
The actual solution for this as of v11 is pg_verify_checksums
(renamed to just pg_checksums for v12). I don't think there's
any really convincing answer before v11.
regards, tom lane
d; maybe you'd get more support for your thesis somewhere
other than here.
On the client side, certainly there are specific applications that
are Windows-centric.
regards, tom lane
n general, a section in the CREATE FUNCTION documentation of two or three
> paragraphs with a few examples and general guidelines would be very helpful.
> I would be happy to write it if someone will explain it to me.
Have at it ...
regards, tom lane
types than ordinary
query contexts, meaning you might also need an explicit cast:
SELECT ARRAY[
'*', '*', 'А', 'А', 'А', 'А', 'А', 'А', 'А', 'А',
...
]::text[];
Try it without first, but if it moans about the query returning the
wrong type, that's how to fix it.
regards, tom lane
-inflicted damage from trying to mix two different levels of
abstraction -- namely, the information_schema and the underlying
native PG catalogs. I'd suggest recasting this as a join between
pg_catalog and pg_attribute, which would make the join condition
just "where c.oid = a.attrelid".
regards, tom lane
eally only firing on one cylinder today :-(
regards, tom lane
", is just ridiculous. If the word after SET is not a known
GUC name then we probably have misconstrued the context, as indeed is
happening in your example; and in any case DEFAULT is about the least
likely thing for somebody to be trying to enter here. (They'd probably
have selected RESET not SET if they were trying to do that.)
regards, tom lane
that's not really "stable", since it depends on random()
which is volatile.
regards, tom lane
ember any optimization for that, but I might be
wrong. Looking at the comments in the plpgsql portion of the
aforementioned commit would probably give more info.
regards, tom lane
n* see later effects); but this usage seems
safe enough.
regards, tom lane
n
postgresql.conf. One idea that came to me while thinking about the syntax
error is that maybe you have one of the other configuration-file-name
variables pointing to pg_hba.conf. That error message tells us that the
server is trying to read pg_hba.conf, right enough, but it doesn't
actually say what it's expecting to find in that file ...
regards, tom lane
is.
I'm still suspicious that the server is reading pg_hba.conf but trying
to interpret it as some other kind of config data, so I'd advise again
to double-check what you've put in postgresql.conf.
regards, tom lane
sage would reflect PII that had not
been supplied by or available to the client.
regards, tom lane
hese GUCs?
And/or put in some kind of test for recursive opening of the same
config file? I don't think it'd occurred to anyone that it's this
easy to get the code to try to do that.
regards, tom lane
at situation. We have
no idea about the structure of the client-side logic.
BTW, I notice that ExecBuildSlotValueDescription punts and never prints
anything if the table in question has RLS enabled. So maybe a workable
kluge for the OP is to enable RLS?
regards, tom lane
nce otherwise there's no certainty that it
won't leak data you don't want leaked. On the whole, I think the right
response to this complaint is that equal attention has to be given to
securing error logs on the client side.
regards, tom lane
ail) = (null).
The DETAIL in this case would be the same whether joe had select(email)
privilege or not; the email value is considered OK to report since it
came from the query not the table.
regards, tom lane
David Gauthier writes:
> What I would like is to see a list of all the tables in the dvm schema and
> nothing else. "\d dvm.*" works, but it also spills the details of every
> table. I just want the list of tables in the schema.
Try "\dt dvm.*".
regards, tom lane
to become the default sort order for uuid
you'd have to remove the opcdefault marking from uuid_ops and attach
it to this opclass instead. No, I'm not sure that that wouldn't have
unpleasant side-effects.
regards, tom lane
REINDEX with VACUUM. It seems like a pretty poor
substitute for that --- it's much more expensive and has worse locking
requirements.
regards, tom lane
ing you could do to triangulate is to verify that v11 pg_dump
is okay working against the v10 server. Unfortunately the other
combination can't be tested, but this'd be enough to exonerate the v10
server side.
regards, tom lane
Ben Snaidero writes:
> Do these stack traces shed help at all?
None worth mentioning :-(. Can you rebuild with debug symbols?
regards, tom lane
t there's a bug that also affects later versions.)
regards, tom lane
r that.
v12 will improve that somewhat.
regards, tom lane
t resolve the issue.
regards, tom lane
et()
in hopes of clearing the problem --- except that I think the
transmission of the reset command is done over the same IP socket
that stats data goes through, so how'd it get through if that's
being blocked?
Anyway, bottom line is to pay close attention to the postmaster
log when you restart.
regards, tom lane
27;t seem impossible, but it's definitely not trivial
either.)
You'll have to do some kind of workaround like assigning the whole array
element to a temp variable, fixing the field in the temp variable, then
assigning back :-(
regards, tom lane
ng my_from_local()'s v_result variable as my_timestamp not record.
regards, tom lane
e core shmem after postmaster start.
regards, tom lane
session can.)
I pushed a fix for this:
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=24c5c711f497c995ad7b560aedd41b4d0f0f77f4
Thanks for the report!
regards, tom lane
to execute just once and return
a tuplestore.
regards, tom lane
text first. It happens that the
expression decompilation code will show you those implicit casts
explicitly, but they don't really mean much.
regards, tom lane
t's idempotent; but only slightly.
regards, tom lane
in use in a particular
> transaction, would require at least that much state be preserved.
Of course, we can't release resources that were acquired by a still-live
subtransaction, a/k/a savepoint.
regards, tom lane
ransaction has failed. But if there's a live
savepoint, then we should enforce it since resources may still be
held. Seems like a bug, if your observation is accurate.
regards, tom lane
iscussed in the thread are still live: should there be a run-time not
only trigger-creation-time privilege check, and if so what should it
check exactly? And is a separate TRIGGER privilege even reasonable,
rather than just saying you must be table owner to create a trigger?
regards, tom lane
hich case you can
rely on this alias type that orafce creates. But you do then have
two types named "date" in the system, so you have to be careful
about search_path settings or you'll get more confusion than it's
worth.
regards, tom lane
ads;
CREATE SCHEMA
regression=# create table "ads"."MyTableName" (f1 int);
CREATE TABLE
regression=# select * from "ads"."MyTableName";
f1
(0 rows)
I'm wondering a bit about invisible white space in your schema
name; but without a self-contained test case we can do no more
than guess.
regards, tom lane
TO is fine
if it's a single-row result. Otherwise, consider looping through
the result with a FOR loop. Again, there are plenty of examples
in the manual.
regards, tom lane
tisfying the workflow_id+status
conditions had no entries with deleted_millis <= 0 either. So these
two test cases visited exactly the same number of index entries, and
any differences in "buffers hit" had to be chance layout effects, or
possibly the result of different index entry sizes. How large is
that "result" column in reality?
regards, tom lane
.
But having said that, it's not clear to me whether Aurora's storage
engine shares this bug with community PG, or you're seeing some
independent bug of theirs that happens to have a similar symptom.
It's even less clear whether AWS would have applied the fix yet if it
is a shared bug. You really need to discuss this with AWS support.
regards, tom lane
n-determinstic.
> If you want to ensure the lowest valued nb is chosen you need to sort the
> *subquery*.
The "weather_reports" example here might help clarify this for you:
https://www.postgresql.org/docs/current/sql-select.html
regards, tom lane
er modification
of the template's pg_class catalog would be
lost.
The comment about only pg_class being affected is my interpretation
of what the commit message said, but I might have misunderstood.
regards, tom lane
t; seconds.
Perhaps an "ANALYZE table_b" in between would help.
regards, tom lane
"Michael P. McDonnell" writes:
> On Sun, May 7, 2023 at 4:25 PM Tom Lane wrote:
>> Perhaps an "ANALYZE table_b" in between would help.
> Okay - that worked.
> How did you know that would work? That's incredible.
Well, I guessed ;-) ... but it was a we
ion are not very intelligible.
https://wiki.postgresql.org/wiki/Slow_Query_Questions
One thought is that you might need to raise from_collapse_limit and/or
join_collapse_limit to at least 15 to get the planner to do a complete
search of the join-order space.
regards, tom lane
strategy is to blame.
regards, tom lane
1701 - 1800 of 2962 matches
Mail list logo
