"Joshua D. Drake" writes:
> On 06/04/2018 01:46 PM, Tom Lane wrote:
>> ... The reason for this is an unfortunate situation that took place in
>> the FreeBSD community awhile back [1], wherein one community member was
>> abusing another via Twitter, and their ex
again in response to the current discussions.
regards, tom lane
end up there too.
(I believe there are plans afoot to move all the "locked" wiki pages'
content to the main site, but I'm not involved in making that happen.)
regards, tom lane
Geoff Winkless writes:
> On Sun, 3 Jun 2018 at 22:47, Tom Lane wrote:
>> In any case, we went over all these sorts of arguments at excruciating
>> length in 2016. It's quite clear to the core team that a majority of
>> the community wants a CoC. I don't t
Adrian Klaver writes:
> On 06/03/2018 11:29 AM, Tom Lane wrote:
>> https://wiki.postgresql.org/wiki/Code_of_Conduct
>> We are now asking for a final round of community comments.
> My comments:
> 1) Reiterate my contention that this is a solution is search of problem.
As
ation where
not-so-civil interactions were common, I agree that it likely wouldn't
work.
regards, tom lane
er actually done any
such thing, and I'd like to think that the CoC committee will never need
to ban anybody either. But if it does come to that, we'll have a much
better governance mechanism in place for it.
regards, tom lane
etails of the process are there to try
to fix point 3.
Yeah, managing the committee is a lot of overhead that in an ideal
world we wouldn't need, but I think we have to accept it to have a
process people will have confidence in.
regards, tom lane
seqscan-and-sort wins
if the need is to fetch the whole table.
regards, tom lane
the sense to
walk away. (Maybe we could put something in the CoC about that, but
I have the sense that it'd do more harm than good.)
regards, tom lane
he situation, thus driving
away people who might otherwise have joined the community.
I'm getting a little tired of people raising hypothetical harms and
ignoring the real harms that we're hoping to fix. Yes, this is an
experiment and it may not work, but we can't find out without trying.
If it turns out to be a net loss, we'll modify it or abandon it.
regards, tom lane
e the
errors stop, and all will be well. But an update would be prudent to
prevent it from happening again.
regards, tom lane
geeks ;-). So I suspect that the pool of potential members
is not really very large. Plus, since we put a time limit on how long
people can serve, we're going to need a fresh set of faces every couple
years. So we shouldn't fool ourselves about how much we're going to be
able to as
Adrian Klaver writes:
> On 06/05/2018 04:41 PM, Tom Lane wrote:
>> I'm getting a little tired of people raising hypothetical harms and
>> ignoring the real harms that we're hoping to fix. Yes, this is an
>> experiment and it may not work, but we can't find ou
tinct-ification processing into a separate
plan node.
agg(... ORDER BY ...) has got the same problem, and it'd likely be
advisable to fix that at the same time.
regards, tom lane
be objects in the
schema that are left over from a crashed session that previously had
the same BackendId. We only make an effort to clean out such objects
at the time that a session first creates a temp object.
In any case, I think you're right that this isn't exposed at the SQL
level presently.
regards, tom lane
elp
in investigating that.
regards, tom lane
removal from the committee or core is another
possible sanction, in addition to those mentioned above.
regards, tom lane
in my proposed addition, and then we're good.
regards, tom lane
ink in the CoC traffic is likely to be the individual
committee members' email accounts --- I trust they'll take some suitable
precautions.
regards, tom lane
s a lot of recently-dead rows at either
extreme of the range of table1.source_id or table2.id?
We made a fix last year to improve that:
https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=3ca930fc3
but it wasn't back-patched.
regards, tom lane
Jerry Sievers writes:
> Tom Lane writes:
>> Oh, hmm, yeah it could be ye olde get_actual_variable_range() issue.
>> When this happens, are there perhaps a lot of recently-dead rows at either
>> extreme of the range of table1.source_id or table2.id?
> We noticed the c
tell us that is helpful for us to know
about your potential involvement with the CoC Committee?
regards, tom lane
[1] https://wiki.postgresql.org/wiki/Code_of_Conduct
nd if so whether that's worse than a "custom" plan
for the specific parameter value.)
If the job_id column has fairly uniform statistics, this exercise
probably won't turn up anything surprising ... but if it doesn't,
we might find that the issue comes from a stupidly chosen generic
plan.
regards, tom lane
war or driving away either person. They may not always succeed. But not
trying is not a better answer.
regards, tom lane
... which *is* spelled
out in the document.
regards, tom lane
tion, btw. ;-)
We didn't get around to implementing that till v10.
regards, tom lane
ly much
worse) planner range estimates. I'm unsure if that's a good tradeoff or
not.
regards, tom lane
database has an OID of 0?
Well, none do, so the correct question is what is passing an invalid
database OID to the code that's complaining. This sure looks like a
bug, though I'm not sure we have enough info to locate it.
regards, tom lane
t for the old cluster, as well as
"select datname, datfrozenxid from pg_database" output from the
old cluster.
regards, tom lane
ately, I don't know anything about how to adjust that
in Windows. A brute-force way would be to issue "set client_encoding"
in your scripts, but there may be a better way.
regards, tom lane
et burnt.
As of 9.6, there are more guarantees in this area than there used
to be (cf commit 9118d03a8), but I don't think it matters as long
as you write an ORDER BY.
regards, tom lane
ries.
If that doesn't fix it, (b) could perhaps be alleviated by adopting
connection pooling, though that has costs of its own.
regards, tom lane
erving to defeat selection of an indexscan.
Why it's corrupt, I dunno, but you might try forcing a reindex on the
master.
regards, tom lane
rection. If the standby's OS
sorts strings differently than the master does, the index will seem
corrupt to it, even if it's fine on the master.
regards, tom lane
s it's worth at least clarifying the docs about this,
Don't the docs describe the behavior pretty clearly already?
regards, tom lane
cal crash recovery to me: corrupt shared
memory contents are expected and recovered from after a crash. However,
we don't expect postmaster.pid to get mucked with.
regards, tom lane
Andres Freund writes:
> On 2018-06-18 12:30:13 -0400, Tom Lane wrote:
>> Sherrylyn Branchaw writes:
>>> LOG: server process (PID 138529) was terminated by signal 6: Aborted
>> Hm ... were these installations built with --enable-cassert? If not,
>> an abort trap s
ing the postmaster manually
if it died. Maybe don't do that repeatedly without human intervention;
but PG is pretty robust against crashes. We developers crash it all the
time, and we don't lose data.
regards, tom lane
espace instead of relying on regnamespace.
regards, tom lane
uot;timing off"
to the EXPLAIN options, then that's probably a factor in making
the Agg node look relatively expensive.
regards, tom lane
for tsvector, which stores
lexeme offsets in 20-bit fields (cf WordEntry in
src/include/tsearch/ts_type.h). Perhaps that was short-sighted but
I don't foresee it changing anytime soon. You'd more or less need
a whole new datatype ("bigtsvector"?) to make it happen.
regards, tom lane
least some of the joins to tt_eotb1 might be unnecessary?)
regards, tom lane
found a way to reach this error without
having waited a few hours beforehand. And we are *not* going to promise
to fix all the performance issues you will hit with a schema design like
this. Redesign. Please.
regards, tom lane
deration?
Nothing's actually happened since then ... it's still under consideration,
but we have to settle on a way of controlling it.
regards, tom lane
es '*.*'" might work, too.
Be careful about shell-command quoting.
regards, tom lane
text,text,boolean), row 66 in
> EXECUTE
I guess audit_sq is a sequence? It looks to me like this function has
not been taught about the changes in sequence metadata in PG v10.
You need to update it, or talk to its author about an update.
regards, tom lane
b-select as I suspect you're thinking.
In short: WITH has lower syntactic precedence than UNION/INTERSECT/EXCEPT.
You need parens if you want it to work the other way 'round.
regards, tom lane
;t-update problem
is related to the fuzzy behavior of floating-point columns. Just
because a float8 value prints out as "1.2345" doesn't mean that it'll
be considered equal to a value you write as "1.2345". If this fact
astonishes you, you should likely switch to type numeric.
regards, tom lane
wrong so far as text output is concerned.
If you retrieve data in binary format, though, it looks like you get
the raw (un-rotated) timestamp value, so that any conversion would have
to be done on the client side.
regards, tom lane
ike it's related to pg_authid
or pg_db_role_setting.
regards, tom lane
ki/Slow_Query_Questions
It'd be particularly useful to compare EXPLAIN output in both the
"slow" and "fast" states.
regards, tom lane
ht then need to REINDEX
pg_db_role_setting to get its indexes in sync with it being empty.)
Whether an equally drastic answer is tolerable for your other missing
table(s) depends on what they are...
regards, tom lane
s. However, you can use overloading to define
several functions of the same name, and just write out one for each
range type you actually need this functionality for. I haven't really
seen applications that need so many range types that this'd be
intolerable.
regards, tom lane
some other way of dropping the fractional
second, probably
select current_timestamp(0) at time zone 'utc';
regards, tom lane
PLAIN (without
ANALYZE) output for the slow and fast cases. What I'm wondering about
is whether the shape of the plan changes.
regards, tom lane
gle-user mode and use that to issue
an ALTER USER ... PASSWORD command. As long as your patch doesn't
break single-user mode, you don't need any other escape hatch.
regards, tom lane
ch about the Postgres App packaging so I can't offer any advice
there. I also don't know how hard it is to get the Aqua client you
mention to talk to a nonstandard port number, though I'd guess that it's
possible.
regards, tom lane
nage it etc...
You haven't exactly explained how that wouldn't be equally true of
this hypothetical new thing.
regards, tom lane
t it does *not* set that up to be part of
gcc's default search paths. (Security 1, usability 0.) You need these
configure flags to do much of anything on that platform:
--with-includes=/usr/local/include --with-libs=/usr/local/lib
regards, tom lane
Thomas Kellerer writes:
> But what about the (temp) space needed for e.g. sorting, grouping or
> intermediate results from CTEs or derived tables?
> Is that also controlled through the temp_tablespaces?
Yes.
regards, tom lane
ave AccessShareLock on,
so I'm not quite sure how we could end up with this result. Maybe
the true explanation is more complicated, like an ALTER DROP COLUMN
that committed just as pg_dump was starting. Have you got records
of any DDL being done at that time?
regards, tom lane
tectural reasons the protection is not 100%;
sometimes you can get odd failures like this, essentially due to "clock
skew" between pg_dump's view of the catalogs and the server's view of the
catalogs. As long as it works on retry, I wouldn't worry too much about
it.
regards, tom lane
Right now it seems the nextval is done first, but I would not want to bet
on that staying true in the future. [ experiments some more ... ]
Actually, looks like we have a rule against flattening sub-selects whose
targetlists contain volatile functions, so maybe you'd get away with that
for the indefinite future too.
regards, tom lane
l_days"
> rather than "all_days".
Per the error message, what needs fixing is the SQL function "bdays",
not the matview as such.
regards, tom lane
al sorting?
Dependencies can override the normal sort order, though a dependency
directly between two tables is rare.
regards, tom lane
clear
why hacking CacheInvalidateHeapTuple in this fashion fixes that, or why
we could expect it to stay fixed.
regards, tom lane
o that client and attach to it
with gdb/lldb. Perhaps xcode can do an "attach to running process",
though at this point I'm wondering if it starts extra threads when
it does so.
regards, tom lane
rned that most of the stuff on the TODO list is either
obsolete or hard (sometimes more hard-to-get-consensus-for than hard-
to-do-technically). We don't maintain that list very well :-(
regards, tom lane
oduces
ALTER ROLE joe SET search_path TO "$user", public;
There was a relevant bug fix in March (commit 742869946) ...
are you certain this is a 10.4 server, and not 10.3 or older?
regards, tom lane
Achilleas Mantzios writes:
> On 30/07/2018 16:51, Tom Lane wrote:
>> Hm, that's not happening for me:
> You (and Adrian) are right. This is due to our own tweaking (which I had
> forgotten). Sorry for the false alarm.
It looks like your hack was to work around the bug tha
d of it on the grounds that its semantics were too squishy to
be useful.
What you want is something like
select relname from pg_class c where relkind = 'r' and
not exists (select 1 from pg_index where indrelid = c.oid and indisprimary);
which will give the right answer in all PG versions.
regards, tom lane
I've pushed a patch along that line. Thanks for the report!
regards, tom lane
Rob Sargent writes:
> Exactly. That that is in the "box" made me think a similar blurb for
> the non-index version should be there also.
This seems to have been fixed in v11 but not back-patched.
regards, tom lane
/postgres-.cnf
and then just start the postmaster without any weird switches.
In this way you will avoid breaking PG-specific tools that
expect to find the config file at its standard location.
regards, tom lane
ipt that you intended to set the
env variable just overwrite $PGDATA/postgresql.conf with the right thing.
regards, tom lane
;d need some other API.
If we did change this, then it'd be reasonable to tighten the error
message behavior; but as things stand, sql_fn_post_column_ref doesn't
know what's going on so it's not in a position to throw a reliable
error message.
regards, tom lane
it there waiting for more data, and it'll be holding whatever
locks it had too.
You could adjust the server's tcp_keepalives_xxx settings to make it
notice the connection drop more quickly.
regards, tom lane
in
the title. There's an example in
https://www.postgresql.org/docs/devel/static/app-psql.html#APP-PSQL-PROMPTING
although it's just talking about a color change.
regards, tom lane
ormal
and not worrisome. autovacuum should kick in and do something
about it at 200 million xacts (autovacuum_freeze_max_age).
regards, tom lane
regards, tom lane
Achilleas Mantzios writes:
> On 30/07/2018 17:00, Tom Lane wrote:
>> It looks like your hack was to work around the bug that was fixed
>> properly in 742869946. You should be able to undo that now ...
> On pgsql 10.4 , I reverted (undi
Andres Freund writes:
> On 2018-08-01 10:24:24 -0400, Tom Lane wrote:
>> IMO, the action you need to take is enabling autovacuum. We've
>> seen many many people go down the path you are taking, and it's
>> generally led to no good in the end. Manual vacuuming
regards, tom lane
hree options for schemas, though the details of each
are a bit different (in particular, schema dependencies would be found
in pg_depend not pg_shdepend).
regards, tom lane
ight also care to read up on DROP OWNED BY.
regards, tom lane
that doesn't work, it's time to hire professional help --- there are
several companies that specialize in PG data recovery.
regards, tom lane
Ron writes:
> For columns of type bytea which store image data (PDFs, JPGs, etc) would it
> speed up the ANALYZE process to SET STATISTICS = 0?
Should do, though I'm not sure how much of an effect you'd see.
regards, tom lane
ruser can do is inherent
in being the owner of all the built-in database objects, and that you
cannot get rid of. Objects have to be owned by somebody.
regards, tom lane
e penalty is that high.)
regards, tom lane
g. The reason that EXPLAIN VERBOSE
is helpful here is that you can see whether the function got inlined
or not: do you see a call to the function, or a representation of
its body?
regards, tom lane
Ken Tanzer writes:
> On Mon, Aug 6, 2018 at 7:42 PM Tom Lane wrote:
>> The reason that EXPLAIN VERBOSE
>> is helpful here is that you can see whether the function got inlined
>> or not: do you see a call to the function, or a representation of
>> its body?
> Ther
7;m not sure if such
practices are still popular, but somebody who was doing that would not
appreciate nannyism.
regards, tom lane
re are some external tools floating around that check things
more aggressively, and hence with a higher rate of false positives.
regards, tom lane
"David G. Johnston" writes:
> On Tue, Aug 7, 2018 at 12:31 PM, Tom Lane wrote:
>> Yes. It's supposed to be a syntax check, not a check that the function
>> would work when executed. (Depending on the particular PL you're using,
>> which you didn&#x
oids a round trip to the server, and (b) works further back
than server_version_num, though that issue is probably academic
to most folk at this point (server_version_num appeared in 8.2).
regards, tom lane
n #ifdef there. If you don't have the macro defined,
you want to fail, not silently build an extension without it.
It's possible you need extern "C" { ... } around the macro, too.
regards, tom lane
uot; around the PG_FUNCTION_INFO_V1 macro, too.
Both those macros produce C function definitions under the hood,
and said functions need to not be name-mangled by C++.
regards, tom lane
eak your bad C++ habits.
regards, tom lane
e or less O(log N) (N being the number of rows
in that catalog). But in practice the main constraint is often the
need to obtain locks on the relevant database objects, and that's
really hard to give a prediction for.
regards, tom lane
101 - 200 of 2937 matches
Mail list logo
