lide.
>
A very small sliver in this problem:
The key collision problem could be avoided if the unique and arbitrary keys
were UUID
Many of the other keys should be related to their respective “table of truth”
so the migration is dependant on these being the same across the locations
The res
ne. I can see no advantage in pure
ASCII when there is the potential for the real world to be contributing text.
And there could well be non-ASCII characters lurking in the old dB, especially
since someone set it up to receive them.
Regards
Gavan Schneider
——
Gavan Schneider, Sodwalls, NSW, A
pg_proc.prosrc would seem to be the least change needed to
allow existing usage to move with the new Pg versions (and maybe help pgAdmin
as well)
Regards
Gavan Schneider
——
Gavan Schneider, Sodwalls, NSW, Australia
Explanations exist; they have existed for all time; there is always a
well-known solution to every human problem — neat, plausible, and wrong.
— H. L. Mencken, 1920
plicated than just
trying to restrict the superuser role.
Gavan Schneider
——
Gavan Schneider, Sodwalls, NSW, Australia
Explanations exist; they have existed for all time; there is always a
well-known solution to every human problem — neat, plausible, and wrong.
— H. L. Mencken, 1920
le topic would be
simpler if the case was left alone but that’s a long road ago and I
believe most of the bridges have been burnt :)
Regards
Gavan Schneider
——
Gavan Schneider, Sodwalls, NSW, Australia
Explanations exist; they have existed for all time; there is always a
well-known solution
knowledge of SQL Server and how this is specified there, but the
…DEFFER… syntax is according to the SQL standard
Regards
Gavan Schneider
——
Gavan Schneider, Sodwalls, NSW, Australia
Explanations exist; they have existed for all time; there is always a
well-known solution to every human prob
-missing-numbers-in-a-sequence-with-sql/>
2022 update: this link is now dead, only reporting "There is nothing
here".
$COMMENT$;
Regards
Gavan Schneider
——
Gavan Schneider, Sodwalls, NSW, Australia
Explanations exist; they have existed for all time; there is always a
well-
which matter), and only cause extra db work
when new data is entered (i.e., no ongoing overhead).
Regards
Gavan Schneider
——
Gavan Schneider, Sodwalls, NSW, Australia
Explanations exist; they have existed for all time; there is always a
well-known solution to every human problem — neat, plausible, and wrong.
— H. L. Mencken, 1920
entation) to floating point there will never be
value resolving why there are differences.
I suggest using the comparison that is appropriate to the representation of
those values or fix the design by using the proper representation.
Gavan Schneider
——
Gavan Schneider, Sodwalls, NSW, Australia
E
t (with embedded photos),
and keeping records so disputes can be handled. This is not a high volume
access to the images so there is no real need for optimum filesystem speed to
serve the images… keeping them in the database as bytea is perfectly workable
and will work for data volumes
s accurately emulated, e.g., http://ibm1130.org/emu/
What is truly amazing about old style FORTRAN is that it has a theological
aspect.
What other computer language can give truth to a maxim such as:
IN FORTRAN GOD IS REAL
Gavan Schneider
——
Gavan Schneider, Sodwalls, NSW, Australia
Explanations
s.com/machinist_tables.htm
Gavan Schneider
——
Gavan Schneider, Sodwalls, NSW, Australia
Explanations exist; they have existed for all time; there is always a
well-known solution to every human problem — neat, plausible, and wrong.
— H. L. Mencken, 1920
On 18 Jun 2021, at 9:34, David G. Johnston wrote:
> On Thursday, June 17, 2021, Gavan Schneider
> wrote:
>
>>
>> My approach is to define such fields as ‘text’ and set a constraint using
>> char_length(). This allows PG to do the business with the text in native
&g
in native form,
and only imposes the cost of any length check when the field is updated… best
of both worlds.
Gavan Schneider
——
Gavan Schneider, Sodwalls, NSW, Australia
Explanations exist; they have existed for all time; there is always a
well-known solution to every human problem — neat, plausible, and wrong.
— H. L. Mencken, 1920
s are needed. So the overall performance is proportional
to the number of elements (N) multiplied by the log of the number of
elements, viz., N * log(N)
Regards
Gavan Schneider
——
Gavan Schneider, Sodwalls, NSW, Australia
Explanations exist; they have existed for all time; there is always a
well-
m of “[ … ]” in shell scripts
Gavan Schneider
——
Gavan Schneider, Sodwalls, NSW, Australia
Explanations exist; they have existed for all time; there is always a
well-known solution to every human problem — neat, plausible, and
wrong.
— H. L. Mencken, 1920
;)
Gavan Schneider
——
Gavan Schneider, Sodwalls, NSW, Australia
Explanations exist; they have existed for all time; there is always a
well-known solution to every human problem — neat, plausible, and
wrong.
— H. L. Mencken, 1920
RAM utilisation is totally normal.
That’s not unexpected. The CPU activity should be using the data
held in RAM not spending all those cycles allocating RAM.
Gavan Schneider
——
Gavan Schneider, Sodwalls, NSW, Australia
Explanations exist; they have existed for all time; there is always a
well
ted effort.
OP now has a choice: decrease threads or (seriously) upgrade the
hardware. We in the gallery would love to see a plot of total time to
completion as a function of threads invoked (50-300 increments of 50)
assuming the starting conditions are the same :)
Gavan Schneider
——
Gavan
Note that quote_literal returns null on null input; if the argument
might be null, quote_nullable is often more suitable.
See also Example 42.1. quote_literal(E'O\'Reilly') → 'O''Reilly'
It is even more ugly but would it at least help with t
Gavan Schneider
——
Gavan Schneider, Sodwalls, NSW, Australia
Explanations exist; they have existed for all time; there is always a
well-known solution to every human problem — neat, plausible, and
wrong. The ancients, in the case at bar, laid the blame upon the gods:
sometimes they were remote and
/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include
-I/usr/local/Cellar/openssl@1.1/1.1.1g/include -I/usr/local/include
-I/Library/Developer/CommandLineTools/usr/include conftest.c >&5
configure:13101: $? = 0
configure:13101: result: yes
Regards
Gavan Schneider
—
On 15 May 2020, at 23:24, Tom Lane wrote:
"Gavan Schneider" writes:
HDRS=${HDRS}:"/usr/local/Cellar/openssl@1.1/1.1.1g/include"
...
--with-includes=${HRDS}
If that's an accurate copy of your script, spelling HDRS correctly
would help.
D’oh!
On 14 May 2020, at 23:26, Tom Lane wrote:
"Gavan Schneider" writes:
-bash-3.2$ ./configure --with-openssl \
> --with-includes=/usr/local/opt/openssl/include/openssl \
> --with-libraries=/usr/local/opt/openssl/lib
...
checking openssl
sh-3.2$
-bash-3.2$ /usr/local/Cellar/openssl@1.1/1.1.1g/bin/openssl version
OpenSSL 1.1.1g 21 Apr 2020
-bash-3.2$
Gavan Schneider
——
Gavan Schneider, Sodwalls, NSW Australia
Explanations exist; they have existed for all time; there is always a
well-known solution to
25 matches
Mail list logo
