Hi everyone! Did anyone had a chance to use PL/JS for sp development? Im
working on app that uses JS to work with data and was wandering whether PL/JS
can offer full data management functionality like PL/PgSLQ?
Thanks.
Greg.
Cool, will take a look. Thanks!
--- On Tue, 19/10/10, Itagaki Takahiro wrote:
From: Itagaki Takahiro
Subject: Re: [HACKERS] PL/JS
To: "Terri Laurenzo"
Cc: "Greg" , "pgsql-hackers@postgresql.org"
Date: Tuesday, 19 October, 2010, 3:18
On Tue, Oct 19, 2010 at
Hi guys, got across an interesting problem of passing params to a function in
postgre: is it possible to pass a composite parameter to a function without
declaring a type first?
For example:
// declare a function
create function TEST ( object??? )
object???.paramName // using par
.
Thanks!
From: Pavel Stehule
To: Greg
Cc: pgsql-hackers@postgresql.org
Sent: Mon, 25 October, 2010 17:46:47
Subject: Re: [HACKERS] Composite Types and Function Parameters
Hello
I am thinking, so it isn't possible. There are a general datatype anyelement,
b
Hi Merlin, I completely forgot about hstore! I'll give it a go. Thanks!
From: Merlin Moncure
To: Greg
Cc: Pavel Stehule ; pgsql-hackers@postgresql.org
Sent: Mon, 25 October, 2010 23:52:55
Subject: Re: [HACKERS] Composite Types and Function Parameters
O
it next week in anticipation of that last missing
piece.
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200208021015
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9SpfRvJuQZxSWSsgRAituAJ9t5rFarCQoylBq/467vmALSue9dACg2hxg
GYQWUuPB2uUAxdCismtyOXc=
ble" and "terible" to find the spots
inside of formatting.c
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200209180909
-BEGIN PGP SIGNATURE-
iD8DBQE9iIDvvJuQZxSWSsgRAqRLAJ9gV8oTnMFTsSmQzMdKppNlWW/TvACgvDu2
f0TDVbi//F5jwZn7K9+9wLE=
=TIs7
-END PGP SIGNATURE--
ser to override the default behavior and always call the
pager, regardless of vertical or horizontal dimensions.
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200211070746
-BEGIN PGP SIGNATURE-
Comment: http://www.turnstep.com/pgp.html
iD8DBQE9ymGFvJuQZxSWSsgRAvKvAJ9qzB76
other arguments out there?
FWIW, I use the tags often in some scripts that rely on the output
of 'cvs status -v'. Seeing REL7_3_STABLE at the top of the
"Existing Tags" list is a bit disconcerting when you know that
it's not true. My scripts assume that the latest releas
64.49.215.6
It would be nice if one or more nameservers were added that
were not in the same subnet, especially because we have so
many mirrors (subdomains) that are scattered all over the globe.
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200301051008
-BEGIN PGP SIGNATURE
.org
If the banner ads (as previously stated) do not bring in much revenue,
is there a reason to keep them?
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200301061347
-BEGIN PGP SIGNATURE-
Comment: http://www.turnstep.com/pgp.html
iD8DBQE+GdDHvJuQZxSWSsgRAhuTAJ9WTsJnBIZfwr
and the streaming audio uses up even more than
> that.
Sounds like the mirrors could easily absorb more of the traffic from the
main page, especially once we get an easier mirroring system in place.
--
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200301130923
-BEGIN PGP SIGNATU
ckslash commands are not amenable to putting inside a
view, as they actually compromise multiple SQL calls and some logic in
the C code, but a few could probably be made into views. Could whomever
added that particular TODO item expand on this?
--
Greg Sabino Mullane [EMAIL PROTECTED]
PGP
g in, and can we (the community)
provide an alternative to this income, perhaps via direct contributions?
--
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200301131149
-BEGIN PGP SIGNATURE-
Comment: http://www.turnstep.com/pgp.h
people to upgrade to 7.3 and spend my energies
on other things. If there is still a strong interest however, I can easily
help out and share what I have already done.
--
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200301161656
-BEGIN PGP SIGNATURE-
Comment: htt
rk against all 7.3+
servers, but I still fail to see the pressing need for a backward-compatible
version when the correct one is always shipped with the server.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200301221120
-BEGIN PGP SIGNATURE-
Comment: http://www.tu
he security of the project by providing a
false sense of security. I think this list would be a good place to discuss
how it would be implemented.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200302030948
-BEGIN PGP SIGNATURE-
Comme
t most of those, especially the last two. This will
not be that easy of a process, but on the other hand, new versions do not
appear very frequently, and it is important to get this right the first time.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200302041207
-BEGI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Can someone point me to an online doc to read through on this?
http://www.desktoplinux.com/articles/AT3341468184.html
http://www.gnupg.org/gph/en/manual.html
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200302041
oup has the ability to revoke it in case of an emergency.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200302071451
-BEGIN PGP SIGNATURE-
Comment: http://www.turnstep.com/pgp.html
iD8DBQE+RBJovJuQZxSWSsgRAh3XAJ47eL56YmSKXJCtdAsyYzByMi+m2QCcCNjm
b1tQyp1zLxkpGjhUer6FpZQ=
=Hf
he tarball, an additional level of
security. MD5 provides an integrity check only. Any security it
affords (such as storing the MD5 sum elsewhere) is trivial and
should not be considered when using PGP is standard, easy to implement,
and has none of MD5s weaknesses.
- --
Greg Sabino Mullane
;
find a unique value that is not already in foo
store this value inside of foo
insert row;
}
commit;
Solution three: use your strategy two, but throw a loop around it and have
it try again (with a new value) if it gets a unique violation.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key:
producing this:
3
chocolate
2
vanilla
> (If, for whatever reason, we go the "processing-oriented" route, then I
> claim that there should not be a different output with and without \x
> mode.)
I agree with this.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x1
we can return
other information (FILE, LINE, etc.) with different variables. This
should all be doable without a protocol change, as long as everything
is returned as a string in a standard format.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200303041516
-BEGIN PGP SIGNATUR
t the TODO page.
Which brings up another question - if a protocol change doesn't warrant
a bump to 8.0, what does? :)
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200303040645
-BEGIN PGP SIGNATURE-
Comment: http://www.turnstep.com/pgp.html
iD8DBQE+ZC1LvJuQZx
pon install?
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200303061015
-BEGIN PGP SIGNATURE-
Comment: http://www.turnstep.com/pgp.html
iD8DBQE+Z2bvvJuQZxSWSsgRAhOnAJ9bU3U11TIOuFyPn338Elx9whsO0gCgm/sX
zuiAS4rFB5hYhk0LuxvGMQE=
=9ntO
-END PG
mple
reformatting of the query results from psql. If not, we should remove
that TODO item form psql and add a different one to the backend section.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200303061020
-BEGIN PGP SIGNATURE-
Comment: http://www.turnstep.com/pgp.ht
("Postgres"?)) If it fails, send mail to
webmaster and exit. If it succeeds, run mv $1.temp $1.html. Or use cp
instead of mv and you have a copy of the previous page always preserved.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200303111731
-BEGIN PGP SIGNATURE---
ook into this; hopefully someone will have started something before then.
If so, count me in as willing to help as well.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200305301423
-BEGIN PGP SIGNATURE-
Comment: http://www.turnstep.com/pgp.html
iD8D
Auguest 1?
Well it would certainly be nice if CVS was working first. I am still
getting the following error:
$ cvs update
/projects/cvsroot: no such repository
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200306101553
-BEGIN PGP SIGNATURE-
Comment: http://www.t
/cvsroot
CVS password:
cvs login: authorization failed: server anoncvs.postgresql.org rejected
access to /projects/cvsroot for user anoncvs
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200306102252
-BEGIN PGP SIGNATURE-
Comment: http://www.turnstep.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Since libpq now keeps track of transaction state, it would be a simple
> matter to add a prompt-string % construct to show something that indicates
> the state
greg=> SELECT 'I am idle';
greg=*> SELECT 'I am in a t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> - allows us to say that PostgreSQL ships with field-tested
> replication in the source tree
We have a winner! I think this one trumps all the rest.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200307160920
-BEG
ath...") and have all subsequent
requests on the same database handle use that schema.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200307231328
-BEGIN PGP SIGNATURE-
Comment: http://www.turnstep.com/pgp.html
iD8DBQE/HsXXvJuQZxSWSsgRArfEAJ4+mIE7fT
see ctid handling beefed up at the
same time. For example, some operators such as != would be nice and might
ease the pain a little for people used to using oids as their "tuple id" :)
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200309291818
-BEGIN PGP S
AND c.relname = $1
AND c.oid = a.attrelid
AND a.attname = $2;
' LANGUAGE SQL;
Usage: SELECT nextval(seqname('tablename','colname'));
You might also want to simply keep a table of the sequence names
if you plan on doing this a lot, or make sure you name them in
a consistent and
unk in the patch kind of surprised me. Do we dump
node trees with -> notation currently? I thought they normally all
looked like sexpressions.)
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
here are cases where the planning time increases
quickly that would be something to code against.
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
i
Wang's tool saved if anyone else wants to take it up. I would say it's
on my TODO list but that's more of an abstract concept than an actual
list.
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Sat, Mar 5, 2016 at 12:59 PM, Greg Stark wrote:
> Well. Not dealt with yet. I think it's more or less clear how to
> tackle it using macros and builtins now but there's a lot of drudgery
> work to actually rewrite all the checks. I have the reports from Xi
> Wang'
reply and was saying not to cross-post like that in the first
place. I see you removed them in your response too which is good but I
missed that and responded to the previous message.
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes t
ll.
Amazing data.
What query is that lone data point that took 8ms instead of 6ms to
plan in both charts (assuming it's the same data point)?
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
involved are large, and index-scanning a large relation
> tends to lose to sorting it. So it just seemed like a dead end.
This is the first message on this subthread that actually gave me a
feeling I understood the issue under discussion. It explains the
distinction between plans that are para
orst case it's only a 30% slowdown and the speedup in the more realistic
scenarios looks at least as big.
I want to rerun these on a dedicated machine and with trace_sort enabled so
that we can see how many merge passes were actually happening and how much
I/O was actually happening.
--
greg
On 12 Mar 2016 10:58 pm, "Tom Lane" wrote:
>
> I wrote:
> > That's confusing because it implies that -fno-common is the default,
> > which it evidently is not. But anyway, my diagnosis is that you're
> > breaking something about the linker's behavior with that switch.
> I shall get rid of the co
low end hardware to go with the low end work_mem settings. This gave
> the patch the benefit of using quicksort to make good use of what I
> assume is a far smaller L2 cache; certainly nothing like 6MB or 12MB.
> I think Greg might have used a home server to test my patch in [1],
> actually
roperties that don't affect equality since I think there are
actually very few of them.
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
unning the
database and you can take lots of snapshots with relatively little
overhead. Having dozens or hundreds of snapshots would be unacceptable
performance drain in production but for testing it should be practical
and they take relatively little space -- just the blocks changed since
the snapsho
esolved the issues authoritatively.
Making decisions in a consensus-driven community is just hard and we
could use some lessons in how to say no or how to resolve
irreconcilable conflicts but barring solving those issues it would at
least be nice to remove them from the critical path blocking other
On 29 Jan 2016 11:58 pm, "Robert Haas" wrote:
> It
> seems pretty easy to construct cases where this technique regresses,
> and a large percentage of those cases are precisely those where
> replacement selection would have produced a single run, avoiding the
> merge step altogether.
Now that avoi
On 30 Jan 2016 8:27 am, "Greg Stark" wrote:
>
>
> On 29 Jan 2016 11:58 pm, "Robert Haas" wrote:
> > It
> > seems pretty easy to construct cases where this technique regresses,
> > and a large percentage of those cases are precisely those where
er. You can statically decide how many tapes you can buffer in
memory based on work_mem and merge until you get N/workers tapes so
that a single merge in the gather node suffices. I would expect that
to nearly always mean the workers are only responsible for generating
the initial sorted runs
more on these machines.
The invariant is just that the deadlock timeout needs enough head room over
the actual time the tester's queries take. If they normally take a 1/10th
of a second then why not just set the timeout to 10x however long they take
on the clobber animals?
--
Greg
e SIGCHILD
handler this is something to beware of. It's not entirely clear to me
that the mention of SA_NOCLDWAIT is the only way to get this
behaviour, at least one stackoverflow answer implied just setting
SIG_IGN was enough.
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@pos
track it
continuously there is neither too little nor too much contention on
this shared memory variable. Also the behaviour would be not too
chaotic if there's a user-tunable minimum and the other activity in
the system only controls how more memory it can steal from the global
pool on top of that
ving system intentionally have some kind interlock to ensure that
the parent has called waitpid before the child execs the shell.
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
;t want the extra "timestamp" keyword before
the column there -- in the examples that's part of the literal being
used to have it be read as a timestamp.
https://www.postgresql.org/docs/8.4/static/functions-datetime.html#FUNCTIONS-DATETIME-EXTRACT
--
greg
--
Sent via pgsql-hackers
On Wed, Aug 17, 2016 at 4:22 PM, Robert Haas wrote:
> We've supported having joins in a DELETE since PostgreSQL 8.1.
Er, yes. Though he does say he's trying to use the same syntax as select...
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To ma
ce
shows that separating DDL and making it static while the DML is
dynamic is just a better design.
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
suspect they mostly become valid since float8in will handle
NaN and the like.
Incidentally, I so wish this module were named "vector" instead of
cube. I don't think I was confused by it for ages and still find it
confuses me for a few moments before I remember what it does.
--
greg
endency
on the code structure in some far-away scan.
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
rs during an autonomous transaction? What
happens if you use a pl language in the autonomous transaction and if
it tries to use non-transactional information such as prepared
statements?
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subs
ucture for parallel query so
there's at least some shared problem space there.
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
ver.
Autonomous transactions will certainly need to be read-write so the
question then is what problems led to the restriction in parallel
query and are they any more tractable with autonomous transactions?
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make c
ame page,
parse the same page header, follow nearby line pointers...? I'm not
sure how effective all that caching is today but it doesn't seem
impossible to imagine getting that all optimized away.
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make chan
suggested. This is just a large unsorted list that we need to
iterate throught. Just allocate chunks of a few megabytes and when
it's full allocate a new chunk and keep going. There's no need to get
tricky with estimates and resizing and whatever.
--
greg
--
Sent via pgsql-hackers m
reduce
the random i/o from switching tapes.
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
nywhere else where there are unintentional
dependencies.
I haven't followed the thread closely but I'm puzzled why you would
need to use bit twiddling to set a floating point number. Isn't there
a perfectly good way to calculate the value you want using ldexp() and
other standard C librar
o unlearn a million instructions
warning not to use this feature and c) The fear of breaking existing
users use cases and databases would be less and pg_upgrade would be an
ignorable problem at least until the day comes for the big cutover of
the default to the new opclass.
--
greg
--
Sent via
Hm, the danger there is once I start refactoring things I could get
bogged down... I would love to remove all the #ifdef's and have the
macros just be no-ops if they're compiled out for example...
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make chan
d initialized memory. But I was unable to test it because
msan didn't work for me at all. This seems to be the way of things
with llvm. It's great stuff but there's always 10% that is broken
because there's some cool new thing that's better.
--
greg
--
Sent via pgsql-ha
like password
hashes or personal data with details censored without giving them
access to the unhashed password or full personal info.
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
: look up
all the records (or just the last record) that modified a given block.
Instead of having to scan all the wal you would only need to scan the
checkpoint eras that had touched that block.
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make change
imum size
regardless of how long a time range they span so if you keep one
changelist for every 10 checkpoints or every 100 checkpoints you could
reduce the storage needs and only lose the time precision.
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
We already know this integer overflow checking is non-standard and
compilers keep trying to optimize them out. Our only strategy to
defeat that depends on compiler flags like -fwrapv that vary by
compiler and may or may not be working on less well tested compiler.
So if there's a nice readable an
e_io_concurrency of 1000 actually
means 7485 prefetches). At some point those i/o are going to start
completing before Postgres even has a chance to start processing the
data.
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
h
if it hasn't been
called yet. I'm sure there are problems with doing that in general but
for the specific errors that can happen before pq_init it might be
feasible since they obviously can't have very much shared state yet to
have corrupted.
--
greg
--
Sent via pgsql-hackers mai
years ago but we didn't and if Amit's patch makes hash indexes
recoverable today then go for it.
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
n
> before.
I have a machine sitting idle now too if you have specific ideas of
what to benchmark.
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
e to run a
modern psql against old servers so you can run a benchmark script. For
another there may be binary-only applications or drivers out there
that are using V2 for whatever reason.
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Mon, Oct 10, 2016 at 3:36 AM, Jim Nasby wrote:
> FWIW, Greg Stark did a talk at PG Open about PG performance going back to at
> least 7.4. He did discuss what he had to do to get those versions to compile
> on modern tools, and has a set of patches that enable it. Unfortunately his
On Mon, Oct 10, 2016 at 9:52 PM, Greg Stark wrote:
>
> The code is here:
>
> https://github.com/gsstark/retropg
>
> The build script is called "makeall" and it applies patches from the
> "old-postgres-fixes" directory though some of the smarts are in the
&
t sure
what the net effect is.
The MEMPOOL_FREE doesn't take any size argument and mcxt.c doesn't
have convenient access to a size argument. It could call the
GetChunkSpace method but that will include the allocation overhead and
in any case isn't this memory already marked noaccess b
^~~
Which seems to indicate that clang may not understand the
"pg_attribute_aligned(2)" or perhaps it does and just doesn't take it
into account when generating these warnings.
I'm sure there are other people testing clang -- isn't it the default
on M
able to reproduce them with a minimal test case yet.
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Ah. Here we go:
$ /usr/bin/clang-4.0 -Wall -Wmissing-prototypes -Wpointer-arith
-Wdeclaration-after-statement -Wendif-labels
-Wmissing-format-attribute -Wformat-security -fno-strict-aliasing
-fwrapv -Wno-unused-command-line-argument -Wall -c clang-bug.c
clang-bug.c:54:9: error: use of undeclared
Sorry -- with the obvious error fixed:
$ /usr/bin/clang-4.0 -Wall -Wmissing-prototypes -Wpointer-arith
-Wdeclaration-after-statement -Wendif-labels
-Wmissing-format-attribute -Wformat-security -fno-strict-aliasing
-fwrapv -Wno-unused-command-line-argument -Wall -c clang-bug.c
clang-bug.c:55:9: w
On Oct 20, 2016 5:27 PM, "Noah Misch" wrote:
>
> On Wed, Oct 19, 2016 at 11:08:39AM +0100, Greg Stark wrote:
>
> > The MEMPOOL_FREE doesn't take any size argument and mcxt.c doesn't
> > have convenient access to a size argument. It could call the
> >
ldn't easily be put into a script which I would have said was
desirable -- except I suspect there are situations where Postgres
database scripts need to do a resetxlog. I'm not sure I can think of
any examples offhand but I wouldn't be too surprised.
--
greg
--
Sent via pgsq
ly.
Tools like pgadmin which want to use the view could check for such
users and display a warning or error rather than inaccurate
information.
If there's any support for my recommendation I'm still happy to pick
up the patch again and commit it.
--
greg
--
Sent via pgsql-hackers maili
On Thu, Oct 27, 2016 at 9:53 PM, Merlin Moncure wrote:
> I think we can rule out faulty storage
Nobody ever expects the faulty storage
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailp
This sounds amazing.
My only comment is that LLVM 3.7 is kind of old in the accelerated world of
LLVM. If you have patches to LLVM you need you won't have much success
submitting them as patches on 3.7.
The current stable release is 3.9 and the development snapshots are 4.0. I
know LLVM moves qui
tering a bit better using
BRIN" is a bad idea. It's just the bit about turning a table
append-only to deal with update-once data that I think is overreach.
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
e might be able to maintain
it by editing the table using SQL updates and/or other tools without
having to teach them a particular input format.
The trick would then be to have a preprocessing step in the build
which loaded the CSV/TSV files into hash tables and replaced all the
strings or other t
is small
enough. That would actually result in accurate results which neither
float4 nor float8 guarantee.)
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
s "?column?", 1+1) AS x;
^
HINT: Perhaps you meant to reference the column "x.?column?" or the
column "x.?column?".
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On 23 February 2017 at 13:27, Greg Stark wrote:
> => SELECT "?column"? FROM (select 1+1 as "?column?", 1+1) AS x;
Oops, I missed the typo there:
=> SELECT "?column?" FROM (select 1+1 AS "?column?", 1+1) AS x;
ERROR: 42702: column reference "
the target of the chain isn't
available. That may be something we'll need in the future for other
cases too.
Throwing an error means the user has to retry their query but that's
at least something they can do. Even if they don't do it automatically
the ultimate user will prob
f having uneven partitions if
you have a data distribution skew -- which can happen even if you have
a good hash function. In a degenerate case you could have a partition
for a single hash of a particularly common value then a reasonable
number of partitions for the remaining hash ranges.
--
of object code. The latter consists of only 10
> instructions, or 24 bytes of object code.
I wonder if there's something that could be optimized out of the
normal cmp function but we're defeating some compiler optimizations
with all our casts and aliasing.
--
greg
--
Sent via
1 - 100 of 4963 matches
Mail list logo
