Re: Can we get rid of repeated queries from pg_dump?

2021-08-30 Thread Tom Lane
hubert depesz lubaczewski writes: > On Mon, Aug 30, 2021 at 10:11:22AM -0400, Tom Lane wrote: >> I don't suppose you could send me a schema-only dump of that >> database, off-list? I'm now quite curious. > Asked the owners for their permission. BTW, I think you c

Re: echo of \C foo

2021-08-31 Thread Tom Lane
Matt Zagrabelny writes: > $ \C foo > Title is "foo". > How do I suppress the echo of "Title is..." from psql? The -q switch would do it ... regards, tom lane

Re: PostgreSQL 12 - ERROR: invalid attribute number 2 for ad_user_pkey - Urgent

2021-09-01 Thread Tom Lane
ely? Is your Postgres up-to-date? How about the underlying OS? regards, tom lane

Re: No xmin in pg_database

2021-09-02 Thread Tom Lane
at identical corruption would happen to different installations.) regards, tom lane

Re: Querying a table with jaccard similarity with 1.6 million records take 12 seconds

2021-09-02 Thread Tom Lane
nt of it. If that's not a good characterization of the goal, it'd help to tell us what the goal is. (Just saying "I want to use jaccard similarity" sounds a lot like a man whose only tool is a hammer, therefore his problem must be a nail, despite evidence to the contrary.) regards, tom lane

Re: Query takes around 15 to 20 min over 20Lakh rows

2021-09-02 Thread Tom Lane
timize the extractions. Otherwise, see https://wiki.postgresql.org/wiki/Slow_Query_Questions regards, tom lane

Re: gen_random_uuid key collision

2021-09-02 Thread Tom Lane
But at least it squares with the observation that only that table is having issues. BTW, are you *entirely* certain that your application never inserts non-default values into that column? regards, tom lane

Re: update non-indexed value is slow if some non-related index/fk are enabled

2021-09-05 Thread Tom Lane
uot;, which requires that (a) no indexed column changes and (b) there is room on the same page for the new copy of the row. Ensuring (b) requires running with a fairly low fill-factor, which bloats your table and thereby creates its own costs. Still, that might be worth doing depending on your particular circumstances. regards, tom lane

Re: pg_upgrade - fe_sendauth: no password supplied

2021-09-06 Thread Tom Lane
x27;t recall for sure, but I think you could have made this work by putting the socket path (/Volumes/Free/Upgrade) instead of "localhost" in the .pgpass file. regards, tom lane

Re: Behavior change in PostgreSQL 14Beta3 or bug?

2021-09-06 Thread Tom Lane
uld not be skipping the cleanup. If it is, the threshold for that is too aggressive. Assuming that that choice was made appropriately, I think the advice you propose here will just cause people to waste lots of cycles on VACUUM runs that have only marginal effects. regards, tom lane

Re: How to log bind values for statements that produce errors

2021-09-07 Thread Tom Lane
n advance of knowing whether the query will throw an error.) regards, tom lane

Re: No xmin in pg_database

2021-09-08 Thread Tom Lane
different from 1262, nor could this change of attnums for the surviving rows ever have happened via Postgres-internal processes. I'm about ready to file this under "you broke it, you get to keep both pieces". regards, tom lane

Re: How to observe plan_cache_mode transition from custom to generic plan?

2021-09-09 Thread Tom Lane
ssed this earlier. (The EXPLAIN EXECUTE output itself > does not contain an "Output:" line, so I didn't notice this lack of > parameter substitution in psql.) I think EXPLAIN VERBOSE would add that bit of detail. regards, tom lane

Re: How to observe plan_cache_mode transition from custom to generic plan?

2021-09-09 Thread Tom Lane
eep expecting us to change it. On the other hand, nobody's put forward any improvement proposals.) regards, tom lane

Re: ERROR: control reached end of function without RETURN, except, it is not a function it is a procedure or a nameless block.

2021-09-13 Thread Tom Lane
e. > This is Postgres's bug Yeah, agreed. Looks reasonably simple to fix, though. regards, tom lane

Re: what is pg_stat_activity.query for idle connections ?

2021-09-13 Thread Tom Lane
suspect this is the source. Is '/* DBD::Pg ping test v3.5.3 */' the last > thing it did, but because it's idle now, it's actually doing nothing ? Yes, exactly. regards, tom lane

Re: Basic Questions about PostgreSQL.

2021-09-15 Thread Tom Lane
x27;t want. Single-user mode is pretty limited, because what it really is is single-process mode: there will be no background support processes such as bgwriter, autovacuum, replication support, etc. The system runs, more or less, but performance is not going to be great. regards, tom lane

Re: SELECT FOR UPDATE returns zero rows with CTE

2021-09-17 Thread Tom Lane
fined what results you get. What's the point of doing it like this, rather than just having cte1 return all the columns needed? regards, tom lane

Re: pg_upgrade problem as locale difference in data centers

2021-09-17 Thread Tom Lane
t (incorrectly ordered) indexes on textual columns. If you don't mind reindexing all of those after the update, you could proceed with this plan. Otherwise, pg_dump-and-restore might be a safer idea. regards, tom lane

Re: Remove duplicated row in pg_largeobject_metadata

2021-09-18 Thread Tom Lane
oth would be a no-go, as I cannot INSERT a specific oid to add > one back as far as I know. > So how do I delete only one of the two? Delete by ctid. select ctid, oid, * from pg_largeobject_metadata where oid=665238; delete from pg_largeobject_metadata where ctid = 'pick one'; regards, tom lane

Re: Remove duplicated row in pg_largeobject_metadata

2021-09-18 Thread Tom Lane
7;d think that creation of such duplicates would still be stopped by that unique index. There's something mighty odd here. regards, tom lane

Re: Azure Postgresql High connection establishment time

2021-09-20 Thread Tom Lane
pretty heavyweight things. Even after the connection is complete, there's overhead involved in populating caches and so forth. You'd be well-served to use a connection pooler and/or try to keep an application's connection open once made. regards, tom lane

Re: Timestamp with vs without time zone.

2021-09-21 Thread Tom Lane
ey want unlabeled timestamps to be interpreted in a particular zone. regards, tom lane

Re: Timestamp with vs without time zone.

2021-09-21 Thread Tom Lane
eady covered upthread, the can of worms that that opens is so large that nobody has wanted to try to tackle it as a primitive Postgres datatype. regards, tom lane

Re: Remove duplicated row in pg_largeobject_metadata

2021-09-22 Thread Tom Lane
x27;d be the old PG server version upgraded from, the new server version upgraded to, the versions of pg_upgrade and pg_dump (these probably should match the new server version, but I'm not certain we enforce that), and the pg_upgradecluster script version? regards, tom lane

Re: Faster distinct query?

2021-09-22 Thread Tom Lane
orted to do 86m heap fetches along the way to returning 812m rows, so the data is apparently pretty dirty. It's possible that a preliminary VACUUM to get page-all-visible hint bits set would be a net win. regards, tom lane

Re: Faster distinct query?

2021-09-22 Thread Tom Lane
Michael Lewis writes: > On Wed, Sep 22, 2021 at 2:48 PM Tom Lane wrote: >> The "index-only" scan is reported to do 86m heap fetches along the >> way to returning 812m rows, so the data is apparently pretty dirty. > Do you say that because you would expect many more

Re: statement_timeout vs DECLARE CURSOR

2021-09-27 Thread Tom Lane
on't persist such cursors before we get into the uninterruptible part of COMMIT. regards, tom lane

Re: Nested Schemata, in a Standard-Compliant Way?

2021-09-28 Thread Tom Lane
problems even with taking over the => digraph, never mind single characters. In the end the functionality-versus-problems ratio is just not going to be very good. regards, tom lane

Re: Problem with identity column & related sequences

2021-09-28 Thread Tom Lane
We fixed it in v13, but the changes seemed far too invasive to risk a back-patch [1]. regards, tom lane [1] https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=1281a5c90

Re: statement_timeout vs DECLARE CURSOR

2021-09-28 Thread Tom Lane
re are so many other code paths there. Not sure how to avoid future bugs-of-omission. regards, tom lane

Re: ERROR: unrecognized node type

2021-09-29 Thread Tom Lane
n was, so we can try to understand where the oversight is. regards, tom lane

Re: ERROR: unrecognized node type

2021-09-29 Thread Tom Lane
tachments as this one was. (For reference, it's not showing up in the PG archives.) You're generally a lot better off *not* using screenshots to make your point. regards, tom lane

Re: ERROR: unrecognized node type

2021-09-29 Thread Tom Lane
acktrace from the point of the error? https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend regards, tom lane

Re: Splitting libpq build

2021-10-03 Thread Tom Lane
led as not being worth the maintenance effort, so I doubt you'll find much interest in resurrecting that one. regards, tom lane

Re: Splitting libpq build

2021-10-03 Thread Tom Lane
Igor Korot writes: > On Sun, Oct 3, 2021 at 3:11 PM Tom Lane wrote: >> Having said that, it does work on non-Windows machines to do >> ./configure ... >> cd src/interfaces/libpq >> make -s install > Well, asking people to download the whole source tree just to bui

Re: Splitting libpq build

2021-10-03 Thread Tom Lane
package were to be picked up and redistributed by Red Hat, or Debian, or any other open-source vendor, the very first thing they'd do is strip it of any such copied code. They don't want the management hassle of having to update multiple copies of libpq or mysql-connector or other stuff. regards, tom lane

Re: DELETE ... USING LATERAL

2021-10-04 Thread Tom Lane
table to the query after the additional tables, not before them? Not sure I'd call this a bug exactly, but maybe there's room for improvement. Or maybe there is an actual semantic issue that I'm not seeing right away. regards, tom lane

Re: DELETE ... USING LATERAL

2021-10-04 Thread Tom Lane
Nikhil Benesch writes: > On Mon, Oct 4, 2021 at 1:48 PM Tom Lane wrote: >> My mental model of these things is that the target table is cross-joined >> to the additional tables as though by a comma in FROM [...] > Mine as well. > I just managed to dredge up some history h

Re: DELETE ... USING LATERAL

2021-10-04 Thread Tom Lane
You could, but then you'd be creating a self-join on the target table (and would need to add suitable WHERE clauses to constrain that join). This might be the best near-term workaround, but it does seem ugly and inefficient. regards, tom lane

Re: Using make_timestamp() to create a BC value

2021-10-06 Thread Tom Lane
cept negative year values as meaning BC. Before that, they threw errors. regards, tom lane

Re: Misplaced double quotes in error message

2021-10-07 Thread Tom Lane
le complain about this topic every so often, but I've not yet seen a proposal that would improve matters. regards, tom lane

Re: Regression in PL/PGSQL code using RETURN QUERY with Postgres 14

2021-10-07 Thread Tom Lane
y reported and fixed at https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=e0eba586b regards, tom lane

Re: Error: server closed the connection unexpectedly

2021-10-10 Thread Tom Lane
n; show log_directory; regards, tom lane

Re: Error: server closed the connection unexpectedly

2021-10-10 Thread Tom Lane
Hm. Not much there. You might try turning on log_connections to be sure, but what this looks like is that the connection request never got to the server. Maybe you've got some middleware involved, like pgpool or some other connection pooler? regards, tom lane

Re: Avg/max size of these JSON docs in Postgres

2021-10-12 Thread Tom Lane
azy. The default behavior is first to compress any large field value(s), and then if the row is still too big, push them out-of-line in compressed form. You can modify that strategy on a per-column basis if need be, but I've seldom heard good reasons to. regards, tom lane

Re: Detecting mis-planning of repeated application of a projection step

2021-10-13 Thread Tom Lane
"p...@cmicdo.com" writes: > The 13.4 release notes document the following: >  > Fix mis-planning of repeated application of a projection step (Tom Lane) >  > >  >  The planner could create an incorrect plan in cases where two >  >  ProjectionPaths w

Re: Replication between different architectures

2021-10-13 Thread Tom Lane
er and therefore corrupt on the replica. See https://wiki.postgresql.org/wiki/Locale_data_changes regards, tom lane

Re: NOTIFY queue is at 66% and climbing...

2021-10-13 Thread Tom Lane
rrent notify queue position exactly matches the supposed global minimum position. This corresponds to a known bug that was fixed in 10.16, so I'd suggest upgrading. As a temporary workaround you could restart that server, but likely the problem would recur after awhile. regards, tom lane

Re: Certificate validity error download.postgresql.org

2021-10-14 Thread Tom Lane
time as other major distros. The most probable explanation for the OP's problem seems to be failure to update ca-certificates and/or openssl at all for several years. regards, tom lane [1] https://letsencrypt.org/docs/certificate-compatibility/

Re: Certificate validity error download.postgresql.org

2021-10-14 Thread Tom Lane
lemented OpenSSL's "workaround 1" [2] on RHEL7, but they left well enough alone on newer platforms. They could not have pushed out the DST cert removal much before that cert expired, for fear of causing unnecessary problems elsewhere. So that's why the seemingly short notice.

Re: "two time periods with only an endpoint in common do not overlap" ???

2021-10-14 Thread Tom Lane
gt; (start_1, common_endpoint) overlaps > (start_2, common_endpoint) > )::text > from c; > The result is "true". Seems to me that the doc is therefore wrong Huh? Those intervals have lots of points in common, not only a single point. The documentation is referring to a case like your second example. regards, tom lane

Re: "two time periods with only an endpoint in common do not overlap" ???

2021-10-14 Thread Tom Lane
it seems clear to me in the context of the whole paragraph that "endpoint" means either end of the range. "Boundary point" would be longer but I doubt any clearer. regards, tom lane

Re: "two time periods with only an endpoint in common do not overlap" ???

2021-10-15 Thread Tom Lane
nstance that two time periods with only an endpoint in common do not overlap. regards, tom lane [1] https://www.postgresql.org/docs/current/functions-datetime.html

Re: postgres ssl client certificate authentification

2021-10-15 Thread Tom Lane
options listed below, there is one method-independent authentication option clientcert, which can be specified in any hostssl record. When set to 1, this option requires the client to present a valid (trusted) SSL certificate, in addition to the other requirements of the authentication method. regards, tom lane

Re: PostgreSQL 14: pg_dump / pg_restore error: could not write to the communication channel: Broken pipe

2021-10-15 Thread Tom Lane
ge if you don't use "-h localhost" but instead let it default to a Unix socket? (I don't have any real reason to think that it would change, but we're grasping at straws here.) regards, tom lane

Re: PostgreSQL 14: pg_dump / pg_restore error: could not write to the communication channel: Broken pipe

2021-10-15 Thread Tom Lane
rly. BTW, I think a more likely explanation is "one of the pg_dump or pg_restore worker processes crashed". Why that should be is still a mystery though. regards, tom lane

Re: "two time periods with only an endpoint in common do not overlap" ???

2021-10-15 Thread Tom Lane
e second range's. (I gloss over the question of what to do with NULL endpoints; but the apparent redundancies in the above seem to be meant to define what happens with NULLs.) I submit that our description using half-open ranges is clearer than the spec's. Nonetheless, they're equivalent. regards, tom lane

Re: Wrong sorting on docker image

2021-10-16 Thread Tom Lane
ability to set an ICU collation as a database's default. But you can attach ICU collations to individual text columns, and maybe that would be a good enough workaround. regards, tom lane [1] https://wiki.postgresql.org/wiki/Locale_data_changes

Re: PostgreSQL 14: pg_dump / pg_restore error: could not write to the communication channel: Broken pipe

2021-10-18 Thread Tom Lane
-in software to receive incoming connections". I also have SSH enabled, though that doesn't seem too relevant here. regards, tom lane

Re: Unsynchronized parallel dumps from 13.3 replica produced by pg_dump

2021-10-18 Thread Tom Lane
period. So I'm suspicious that this is an RDS-specific effect, and thus that you should consult Amazon support first. If they say "no, it's Postgres all the way down", then we need to look closer. regards, tom lane

Re: Unsynchronized parallel dumps from 13.3 replica produced by pg_dump

2021-10-18 Thread Tom Lane
differs from the community version by quite a bit, but > I'm unsure how much their regular Postgres offering differs, if at all. Yeah, Aurora is definitely a different beast at the storage level. I'm not entirely sure about RDS. regards, tom lane

Re: Relations between operators from pg_amop and classes of operators from pg_opclass

2021-10-19 Thread Tom Lane
erator is essential to an opclass when it is not really. regards, tom lane [1] https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=9f9682783 [2] https://www.postgresql.org/message-id/flat/4578.1565195302%40sss.pgh.pa.us

Re: pg_class.oid at 4B

2021-10-20 Thread Tom Lane
of short-lived temporary tables, maybe? > Also what happens when pg_class.oid reaches 4B. Nothing. The counter will wrap around and you won't notice a thing. regards, tom lane

Re: Can we get rid of repeated queries from pg_dump?

2021-10-20 Thread Tom Lane
I wrote: > Anyway, it doesn't look like there's much hope of improving this > aspect without a significant rewrite. Just to close out this thread: I've now posted such a rewrite at https://www.postgresql.org/message-id/2273648.1634764485%40sss.pgh.pa.us regards, tom lane

Re: Can db user change own password?

2021-10-21 Thread Tom Lane
could do "SELECT CURRENT_USER" first. I'm not sure if we want to change a security-relevant behavior in released branches. But if we don't, we probably need to change the docs to something like "(by default, the logged-in user)". regards, tom lane

Re: Can db user change own password?

2021-10-21 Thread Tom Lane
Adrian Klaver writes: > On 10/21/21 09:53, Tom Lane wrote: >> I'm not sure if we want to change a security-relevant behavior >> in released branches. But if we don't, we probably need to >> change the docs to something like "(by default, the logged-in >>

Re: Can db user change own password?

2021-10-21 Thread Tom Lane
plicitly say which role it's intending to set the password for: db=> \password Enter new password for role "dbowner": Enter it again: regards, tom lane

Re: Issue with pg_basebackup v.11

2021-10-22 Thread Tom Lane
el realizes that the connection is lost. The actual blame probably resides with some firewall or router that has a short timeout for idle connections. I'd try turning on fairly aggressive TCP keepalive settings for the connection, say keepalives_idle=30 or so. regards, tom lane

Re: Looking for a doc section that presents the overload selection rules

2021-10-22 Thread Tom Lane
-- 22-Oct-2021 +00:00 (1 row) Regardless of whether the original choice not to have this variant was intentional or an oversight, I'd be pretty loath to change it now because of backwards compatibility. But Postgres is adaptable. regards, tom lane

Re: Issue with pg_basebackup v.11

2021-10-23 Thread Tom Lane
Ninad Shah writes: > Would keepalive setting address and mitigate the issue? [ shrug... ] Maybe; nobody else has more information about this situation than you do. I suggested something to experiment with. regards, tom lane

Re: String comparison fails for some cases after migration

2021-10-26 Thread Tom Lane
ed. Did the underlying OS version change? If so, see https://wiki.postgresql.org/wiki/Locale_data_changes regards, tom lane

Re: pg_dump and pg_restore and foreign keys

2021-10-27 Thread Tom Lane
. While a real feature patch that made this optional would be a bit complicated, doing it unconditionally should be a one-line change. regards, tom lane

Re: pg_dump and pg_restore and foreign keys

2021-10-27 Thread Tom Lane
Tore Halvorsen writes: > That would be appending it for "pg_catalog.pg_get_constraintdef(oid) AS > condef" in getConstraints in pg_dump.c? No, you want to mess with the text printed by dumpConstraint(). regards, tom lane

Re: How to Resolve Data Being Truncated or Rounded Up During PostgreSQL Migration from v9.623 to v12.8?

2021-10-28 Thread Tom Lane
lgorithm automatically prints the minimum number of digits needed to ensure exact reload. All the same comments apply to float8, of course, with a different number of digits. regards, tom lane

Re: Postgres dblink example

2021-10-29 Thread Tom Lane
d224008ef98;hb=HEAD regards, tom lane

Re: psql syntax for array of strings in a variable?

2021-10-29 Thread Tom Lane
27;baz regression=# \set foo bar ''baz regression=# \echo :foo barbaz Not sure offhand how well-documented this is. regards, tom lane

Re: Lazier alternative to row_to_json ?

2021-11-01 Thread Tom Lane
he output; though you'd have to provide a layer of dequoting and line-separation logic. regards, tom lane [1] https://www.postgresql.org/docs/current/libpq-single-row-mode.html

Re: to_date() and to_timestamp() with negative years

2021-11-03 Thread Tom Lane
to_date --- 0044-03-15 BC (1 row) I'd be the first to agree that that code is a mess and could stand to be rewritten --- but I seriously doubt that we'd take a patch that intentionally breaks cases that work fine today. There's also the angle that these are supposed to be Oracle-compatible, so I wonder what Oracle does with such input. regards, tom lane

Re: Selectivity and row count estimates for JSONB columns

2021-11-03 Thread Tom Lane
principle this'll produce a far better estimate than any fixed default could provide. If you're coming out with a crappy estimate, you might be able to improve matters by increasing the column's statistics target so that more MCV and histogram entries are collected.

Re: to_date() and to_timestamp() with negative years

2021-11-03 Thread Tom Lane
w the negative-century case works, so it seems sane to do likewise. The last two look like a parsing issue: with no field separator (nope, the space doesn't count), the code is taking the dash as a field separator. regards, tom lane

Re: Debugging features needed

2021-11-05 Thread Tom Lane
, table or function) I would be > more than happy. application_name is meant for that ... regards, tom lane

Re: Determining if a table really changed in a trigger

2021-11-06 Thread Tom Lane
Mitar writes: > Anyone? Any way to determine the number of affected rows in a statement > trigger? Check the size of the transition relation. regards, tom lane

Re: libpq: How to cancel a COPY ... TO statement?

2021-11-08 Thread Tom Lane
al of data down the pipe. You should keep pulling (and discarding) data until you get the end or error response. regards, tom lane

Re: Logical Replication - Should Destination Table Columns Be Defined With Default Value

2021-11-09 Thread Tom Lane
ocument the implications for logical replication better. regards, tom lane

Re: Logical Replication - Type messages?

2021-11-10 Thread Tom Lane
e that namespace is one of >the properties sent with the types)? Some would say that custom types are THE defining feature of Postgres, compared to other SQL implementations. regards, tom lane

Re: I added a ?? operator, the sqrt function is still used internally, but now there is a problem, it affects the := and .. operators of the database

2021-11-11 Thread Tom Lane
share the * same lexer. If you add/change tokens here, fix PL/pgSQL to match! Since you didn't do that, PL/pgSQL is confused about the token codes in use for DOT_DOT and so on. regards, tom lane

Re: pg_restore depending on user functions

2021-11-14 Thread Tom Lane
pected. What minor release are you using? regards, tom lane

Re: pg_restore depending on user functions

2021-11-14 Thread Tom Lane
=?UTF-8?B?0JTQvNC40YLRgNC40Lkg0JjQstCw0L3QvtCy?= writes: > вс, 14 нояб. 2021 г. в 22:31, Tom Lane : >> Usually this is caused by being careless about search_path assumptions >> in your functions ... but with no details, it's impossible to say >> anything with certainty.

Re: pg_restore depending on user functions

2021-11-14 Thread Tom Lane
=?UTF-8?B?0JTQvNC40YLRgNC40Lkg0JjQstCw0L3QvtCy?= writes: > вс, 14 нояб. 2021 г. в 23:46, Tom Lane : >> This is not "details", this is an evidence-free assertion. Please show >> a concrete example of problematic functions. > Ok, I'll do it. > [ example ]

Re: PostgreSQL debug log doesn't record whole procedure(from receiving request to sending response)

2021-11-15 Thread Tom Lane
g(DEBUG) after every line of code in the server, and then high-level debugging logs would be even more impossibly voluminous than they are now. I'd say the existing logging gave you plenty of clue where to look. regards, tom lane

Re: pg_restore depending on user functions

2021-11-15 Thread Tom Lane
=?UTF-8?B?0JTQvNC40YLRgNC40Lkg0JjQstCw0L3QvtCy?= writes: > Is it ok to attach a 5MB data schema or is it not possible? Copy one by one > to a letter? Is it smaller if you omit the data (-s switch)? Shouldn't be relevant here. regards, tom lane

Re: Row estimate on empty tables

2021-11-16 Thread Tom Lane
onally so I would like to confirm. We did improve matters in v14, see https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=3d351d916 (It looks like the v14 release notes say nothing about this, which perhaps was a bad idea.) regards, tom lane

Re: General Performance Question

2021-11-18 Thread Tom Lane
ter. I wouldn't worry about cleaning up unnecessary EXECUTE usage till you have a working port. regards, tom lane

Re: Execute command in PL/pgSQL function not executing

2021-11-19 Thread Tom Lane
ou a better feeling for the work that the plpgsql function has to do. 3. I kind of doubt that outputting a single text column is really the end result you want here. How is it meaningful to be crosstab'ing multiple questions if that's to be the end result? regards, tom lane

Re: insert column monetary type ver 2

2021-11-20 Thread Tom Lane
ep_by_space = 0 '\000', int_n_cs_precedes = 0 '\000', int_n_sep_by_space = 0 '\000', int_p_sign_posn = 0 '\000', int_n_sign_posn = 0 '\000'} A quick lookup later, that's U+202F or "narrow no-break space". cash_in is picky about this, and won't take plain ASCII space as a substitute. Not sure if it should. regards, tom lane

Re: pg_dump insert column GENERATED

2021-11-20 Thread Tom Lane
1, DEFAULT, 1); I wonder what version of pg_dump is actually being used there. regards, tom lane

Re: pg_dump insert column GENERATED

2021-11-21 Thread Tom Lane
27; for the generated column, but maybe we don't? regards, tom lane

Re: insert column monetary type ver 2

2021-11-21 Thread Tom Lane
Ron writes: > On 11/20/21 11:01 AM, Tom Lane wrote: >> A quick lookup later, that's U+202F or "narrow no-break space". >> cash_in is picky about this, and won't take plain ASCII space as >> a substitute. Not sure if it should. > It probably sh

Re: pg_dump insert column GENERATED

2021-11-22 Thread Tom Lane
ave me the clue I needed. If there are dropped column(s) before the GENERATED one, pg_dump gets it wrong --- but only in --inserts mode, not the default COPY mode, which no doubt explains why nobody noticed. There is code in there to inject DEFAULT, but it must be indexing the flag array wrong. Will fix, thanks for the report! regards, tom lane

<    20   21   22   23   24   25   26   27   28   29   >