On 1/9/17 7:22 AM, amul sul wrote:
On Sun, Jan 8, 2017 at 8:50 AM, Jim Nasby wrote:
[skipped...]
Oh, hmm. So I guess if you do that when the background process is idle it's
the same as a close?
I think we need some way to safeguard against accidental forkbombs for cases
where users a
anguage other than C, and could reasonably be ported.
Especially if that could be done in such a way that the net result is
still C code so we're not adding dependencies to non developers (similar
to bison).
Extensions are a step in that direction, but they're ultimately not core
Pos
nced pltcl is one possible solution
for that problem.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
--
Sent via pgsql-hackers mailing l
today.
Being able to check the existence of a variable is a very common idiom
in other languages, so I'm don't see why plpgsql shouldn't have it.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data
On 1/9/17 5:38 PM, Tom Lane wrote:
Jim Nasby writes:
Hmm... I suspect there's more places where this could be a problem. For
example, pltcl_quote calls palloc, which could ereport as well.
Yeah. I looked at that but couldn't get terribly excited about it,
because AFAICS, Tcl in
(though arguably you might not need to be able to
un-assign...).
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
--
Sent via pgsql-
ave 2 explicit namespaces: the top one being auto
variables and the one below that being function arguments. The namespace
below that would be the top-most *user* block.
Both of the pre-defined namespaces need the ability to change their
name; I don't see any issue with using PRAGMA for that.
--
stuck
supporting the old version for a LONG time. A big part of why
standard_conforming_strings was so ugly is users didn't have enough time
to adjust. If we'd had that enabled by default for 4-5 releases it
wouldn't have been nearly as much of an issue.
--
Jim Nasby, Data Ar
Solves the most common
use case and is backwards compatible.
That won't allow you to use a variable in multiple places though... is
there a reason we couldn't support something like IS DEFINED and UNSET?
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics,
On 1/9/17 4:23 PM, Tom Lane wrote:
Jim Nasby writes:
Got a stack trace. The abort happens in TclObjLookupVar:
Yeah, I found the problem: pltcl_returnnext calls pltcl_build_tuple_result
which may throw elog(ERROR), leaving the Tcl interpreter's state all
screwed up, so that later functio
On 1/9/17 3:12 PM, Jim Nasby wrote:
I'm compiling 8.4 now, will see if I can duplicate.
Got a stack trace. The abort happens in TclObjLookupVar:
if (nsPtr->varResProc != NULL || iPtr->resolverPtr != NULL) {
nsPtr itself is NULL.
* thread #1: tid = 0x, 0x0
that's very possibly the only animals running 8.4...
I'm compiling 8.4 now, will see if I can duplicate.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TR
On 1/5/17 12:04 AM, David Fetter wrote:
+errmsg("UPDATE requires a WHERE clause when
require_where.delete is set to on"),
ISTM that message is no longer true.
The second if could also be an else if too.
--
Jim Nasby, Data Architect, B
cludes=/opt/local/include and --with-libraries=/opt/local/lib
to configure, so maybe that's it.
In any case it doesn't bother me enough to investigate it right now. I
just wanted to make sure it wasn't something more serious.
Thanks!
--
Jim Nasby, Data Architect, Blue Treble
| tclsh
8.6.6
Anyway, attached is a complete new patch that fixes that issue (and a
couple test diffs I missed :/), as well as the utf_e2u issue you
discovered. I've applied this patch to master via git apply and run it
through make check-world, so hopefully this puts the horse out to pas
On 1/8/17 5:56 PM, Greg Stark wrote:
On 8 January 2017 at 21:50, Jim Nasby wrote:
Somewhat related to that... it would be useful if Postgres had "fenced"
functions; functions that ran in a separate process and only talked to a
backend via a well defined API (such as libpq). There&#
ough, since it's simpler.
In both cases, I'd really like the ability to rename those blocks.
#pragma would be fine for that.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble!
they haven't done that,
there's nothing preventing them from doing just that. If that happens
we're going to have some very difficult choices to make.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Troub
hose issues down the road...
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
/ then that exactly describes building
non-trivial systems on top of relational databases. The devil is always
in the details.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http
te; use a columnref hook instead. [Tom Lane]
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
--
Sent via pgsql-hackers mailing list (pgsql-hack
ption on
http://llvm.org claims it can be used like Valgrind, which the project
currently supports.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-
.
Hmm... I just thought of something though... do you have PGUSER set?
That might break installworld-check.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855
probably continue to
support that. But in the other direction I don't think it's worth it.
TCL does have a separate string append operation as well, so we'll need
to either provide that or do all the appending using our string
functions and then pass that along.
--
Jim Nasby, Data
's perfectly OK to just break things
without any warning or support, while another part of the project
adamantly refuses any kind of a break at all, even what's breaking has
never officially been supported.
I don't think that dichotomy is good for the community or for our users
On 12/22/16 4:30 PM, Robert Haas wrote:
On Thu, Dec 22, 2016 at 4:41 PM, Jim Nasby wrote:
On 12/22/16 4:20 AM, amul sul wrote:
• pg_background_detach : This API takes the process id and detach the
background process. Stored worker's session is not dropped until this
called.
When I
can be
both painful and error prone).
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
--
Sent via pgsql-hackers mailing list (pgsql-hackers@post
ion of Postgres. That would be a great way to gain knowledge on what
users would want to see in a column store, something else I suspect we
need. It would also be far less code than what you or Alvaro are
proposing. When it comes to large changes that don't have crystal-clear
requirements, I think
we could add better support to existing
commands for at least some of these things. For example, SELECT ... INTO
NOMULTI (instead of STRICT) to indicate that multiple rows are an error
but missing data is OK.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Da
aracter to distinguish variables screws us. :/
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
--
Sent via pgsql-hackers mailing list (pgs
nd
if we wanted to avoid that hassle, we could allow custom GUC settings on
extensions, like we currently do for roles and databases.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://B
file.global.in to check for an environment variable?
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
--
Sent via pgsql-hackers mailing list (pgsql-h
9.4 but there has been some
testing with 9.5.
To make sure this doesn't get lost, please add it to
https://commitfest.postgresql.org. Please verify the patch will apply
against current HEAD and pass make check-world.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Exper
ame that I was
logged in as, instead of the test database name "regress_ecpg_user2". I don't
think this has anything to do with the changes to pg_ctl.
Hrm, I'm not able to reproduce that problem. Can you run make
installworld-check on a checkout of master and see if yo
nce to be added. A schema diff won't know what specifically has
to match, but our code does.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-87
s would be a non-issue if we provided example configs for a few
different workloads. Obviously those would never be optimal either, but
they *would* show users what settings they should immediately look at
changing in their environment.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin T
;ve wanted this many times in the past. If combined with Robert's
idea of a background process that does the expensive time calls this
could potentially provide very useful information for even very short
duration locks.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
E
On 12/28/16 10:26 PM, Robert Haas wrote:
On Wed, Dec 28, 2016 at 1:06 PM, Tom Lane wrote:
Jim Nasby writes:
On 12/28/16 11:25 AM, Tom Lane wrote:
The idea of just capturing the wait start for heavyweight locks, and
not other lock types, still seems superior to any of the alternatives
that
On 1/5/17 5:38 AM, Beena Emerson wrote:
On Tue, Jan 3, 2017 at 2:53 AM, Jim Nasby mailto:jim.na...@bluetreble.com>> wrote:
General comments:
There was some discussion about the impact of this on small
installs, particularly around min_wal_size. The concern was that
...
The
ere. I realize that's
not going to save any significant amount of code, but it would make it
crystal clear what's going on (assuming the excellent comment above
RIGHTMOST_ONE was kept).
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Archite
On 1/6/17 2:17 PM, Tom Lane wrote:
Jim Nasby writes:
On 10/31/16 3:24 PM, Jim Nasby wrote:
This patch increases test coverage for pltcl, from 70% to 83%. Aside
from that, the work on this uncovered 2 new bugs (the trigger return one
I just submitted, as well as a bug in the SRF/composite
On 12/28/16 3:14 AM, Craig Ringer wrote:
On 28 December 2016 at 12:32, Jim Nasby wrote:
On 12/27/16 9:10 PM, Craig Ringer wrote:
On 28 December 2016 at 09:58, Jim Nasby wrote:
I've looked at this some more, and ITSM that the only way to do this
without
some major surgery is to cre
Forwarding some comments I neglected to send to the list...
On 1/3/17 9:16 AM, Peter Eisentraut wrote:
> On 1/2/17 1:04 PM, Jim Nasby wrote:
On 12/31/16 10:17 AM, Peter Eisentraut wrote:
--- a/src/test/regress/expected/event_trigger.out
+++ b/src/test/regress/expected/event_trigger.
tabase values for GUCs.
That said, IIRC GUCs are setup in such a way that could could just
create a new stack upon connection. Actually, I think that'd need to
happen anyway, otherwise these variables are going to look like GUCs
even though they're not.
--
Jim Nasby, Data Architect, B
On 1/3/17 9:20 PM, Amit Kapila wrote:
On Wed, Jan 4, 2017 at 3:47 AM, Jim Nasby wrote:
On 1/2/17 9:47 PM, Tom Lane wrote:
Correct coding would be
volatile TupleDesc desc = slot->tts_tupleDescriptor;
CallbackState * volatile myState = (CallbackState *) self;
PLyTypeI
;ve found hacks to work around this
during extension installation (ie: query pg_extension.extnamespace in
the dependent extension build script), but if the other extension gets
relocated you're hosed.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, D
On 1/2/17 9:47 PM, Tom Lane wrote:
Jim Nasby writes:
In the attached patch (snippet below), I'm seeing something strange with
args->in.r.atts[].
Did you try comparing the apparent values of "args" before and after
entering PG_TRY?
Yeah, see below. FWIW, when I did that
On 1/2/17 3:57 PM, Tom Lane wrote:
Jim Nasby writes:
The recent thread about compiler warnings got me thinking about how it's
essentially impossible to notice warnings with default make output.
Perhaps everyone just uses make -s by default, though that's a bit
annoying since you get
On 1/3/17 11:57 AM, Magnus Hagander wrote:
I've pushed a reset to the master repo. Working on the mirror now.
Please don't forget github. :)
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it
On 1/3/17 10:33 AM, Fabien COELHO wrote:
** PLEASE **
COULD YOU REMOVE THE PARTS OF EMAILS YOU ARE NOT RESPONDING TO WHEN
REPLYING IN THE THREAD?
** THANKS **
+1. Frankly, I've been skipping most of your (Pavel) replies in this
thread because of this.
--
Jim Nasby,
ans to get the old behavior back) then I don't think there's any point
in continuing this thread, because some of these issues can NOT be
reasonably solved by a checker.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
D
t about plpgsql option (function scope) -- WITHOUT-PLAN-CACHE - any
non trivial plans will not be cached - and evaluated as parametrized
query only.
I'd also like the ability to do a "localized" PREPARE; similar to a SQL
level PREPARE statement, but ensuring that the statement got d
gh that someone took
the time to break plpgsql out of the core code and fork it.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
--
Sent via p
ariable that gives you the old behavior).
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
--
Sent via pgsql-hackers mailing list (pgsql-h
The following review has been posted through the commitfest application:
make installcheck-world: not tested
Implements feature: not tested
Spec compliant: not tested
Documentation:not tested
General comments:
There was some discussion about the impact of this on small
sting things like
pg_dump and event triggers.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
--
Sent via pgsql-hackers mailing list (pgsql-ha
ly change those values for a single
function. If you've set extra_errors = 'all' globally, a single function
can't say "turn off the too many rows setting for this function".
BTW, while I can see value in being able to change these settings for an
entire function, I
On 1/2/17 11:39 AM, David Steele wrote:
On 1/2/17 12:30 PM, Jim Nasby wrote:
On 1/1/17 9:48 AM, Peter Eisentraut wrote:
On 12/30/16 9:57 AM, Stephen Frost wrote:
Additionally, people who are actually using these bits of the system are
almost certainly going to have to adjust things for the
be default to throwing an exception.
I think instead of tying these to extra_*, each GUC should accept a LOG
level.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TR
.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
On 1/2/17 1:31 AM, Amit Kapila wrote:
On Mon, Jan 2, 2017 at 11:14 AM, Jim Nasby wrote:
In the attached patch (snippet below), I'm seeing something strange with
args->in.r.atts[]. Prior to entering the PG_TRY block, I can inspect things
in lldb just fine:
(lldb) call args->in.r.a
ereport(ERROR,
(errmsg("missing list for attribute
%d", i)));
/* XXX If the function can't be null, ditch that check
*/
if (slot->tts_isnull[i] || args->in.r.atts[i].func ==
N
On 12/27/16 9:10 PM, Craig Ringer wrote:
On 28 December 2016 at 09:58, Jim Nasby wrote:
I've looked at this some more, and ITSM that the only way to do this without
some major surgery is to create a new type of Destination specifically for
SPI that allows for the execution of an arbitr
On 10/31/16 3:24 PM, Jim Nasby wrote:
This patch increases test coverage for pltcl, from 70% to 83%. Aside
from that, the work on this uncovered 2 new bugs (the trigger return one
I just submitted, as well as a bug in the SRF/composite patch).
Rebased patch attached. Test coverage is now at 85
and global settings being useful, and perhaps
per-user as well. GUCs already have those.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
--
Se
should be good.
That's the whole point of having settings to deal with
incompatibilities: so we can actually fix these warts without breaking
everyone's code, yet also make it clear to users that they should stop
using the warts and instead use the new and improved syntax.
--
Jim Na
t would be a problem. Hence the
point of discussing before proceeding.
Then IMHO what needs to happen is to have a discussion on actual syntax
instead of calling into question the value of the feature. Following
this thread has been very painful because the communications have not
been very cle
but I think that's certainly fine for
pg_stat_activity. Most importantly, it would mean that if something has
gone horribly wrong you'd at least have some kind of relatively accurate
duration to work from.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in
On 12/28/16 7:16 AM, Pavel Stehule wrote:
2016-12-28 5:09 GMT+01:00 Jim Nasby mailto:jim.na...@bluetreble.com>>:
On 12/27/16 4:56 PM, Merlin Moncure wrote:
On Tue, Dec 27, 2016 at 1:54 AM, Pavel Stehule
mailto:pavel.steh...@gmail.com>> wrote:
Which is wh
sumably with no
complaints. There's probably several other compatibility GUCs we could
remove now.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (
a tighter tolerance would help.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresq
On 12/28/16 10:43 AM, David Fetter wrote:
Callbacks aren't easy to find either.
Should callbacks be another chapter in the docs?
That would also be nice, but I suspect that will be harder than finding
all the hooks.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Exper
7;s a reasonably easy way to start that journey here, please
consider doing so.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
--
Sent via
han "variables", but presumably all the other
syntax and settings could be the same. Again, it's not the job of this
proposal to boil that ocean, but it would be nice to leave the option open.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Dat
On 12/27/16 9:10 PM, Craig Ringer wrote:
On 28 December 2016 at 09:58, Jim Nasby wrote:
I've looked at this some more, and ITSM that the only way to do this without
some major surgery is to create a new type of Destination specifically for
SPI that allows for the execution of an arbitr
g a static variable with hook in the name) then you can
verify that there's an appropriate comment block. I'm guessing someone
familiar with tools like doxygen could set that up without too much
effort, and I'd be surprised if the community had a problem with it.
--
Jim Nasby, Da
on, so it would be a lot of work to try and
change that. While there may be some plpgsql-specific problems with it
supporting stored procs, there are much bigger questions to answer
before worrying about that.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data
On 12/21/16 8:21 AM, Jim Nasby wrote:
On 12/20/16 10:14 PM, Jim Nasby wrote:
It would be a lot more efficient if we could just grab datums from the
executor and make a single copy into plpython (or R), letting the PL
deal with all the memory management overhead.
I briefly looked at using SPI
hooks we have, when
they fire and where to find them in code would be sufficient.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
--
Sent vi
s
suggesting about deadlock timeout...)
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
--
Sent via pgsql-hackers mailing list (pgsql-hackers@pos
t least you know the config is valid, the port is
available, etc. That would be much harder to handle externally.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-T
catalog). That's part of the driver for all the discussion about things
like permanent temp tables (which still leaves a bloat and performance
problem in the table itself).
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
which I don't think is the case here, right? I'd
suggest pg_background_close() instead.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-253
de or contents need to be synced. Yes, it sucks.
IIRC this isn't the first time we've run into this problem... should
pg_fsync() automatically fsync the directory as well? I guess we'd need
a flag to disable that for performance critical areas where we know we
don't need it
On 12/21/16 8:39 AM, Tom Lane wrote:
Jim Nasby writes:
On 12/21/16 1:55 AM, Andreas Karlsson wrote:
Does your patch handle "ALTER TYPE name ADD ATTRIBUTE ..."? My immediate
guess would be that it could be a cache invalidation thing.
Won't that only happen at end of tr
On 12/21/16 1:55 AM, Andreas Karlsson wrote:
On 12/21/2016 04:14 AM, Jim Nasby wrote:
Why do functions that accept composite types delay type resolution until
execution? I have a naive patch that speeds up plpy.execute() by 8% by
caching interred python strings for the dictionary key names
On 12/20/16 10:14 PM, Jim Nasby wrote:
It would be a lot more efficient if we could just grab datums from the
executor and make a single copy into plpython (or R), letting the PL
deal with all the memory management overhead.
I briefly looked at using SPI cursors to do just that, but that looks
royal PITA when the xid is a special xid. So
I'd argue that we should effectively remove xid from user's view. Even
if we don't want to bloat pg_class by 4 bytes, we should just make xid
even more opaque than it is today and tell users to just cast it to bigxid.
--
Jim Nasby, Data
nt to call an external interpreter while potentially
holding page pins, but even then couldn't we just copy a single tuple at
a time and save a huge amount of palloc overhead?
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and Postg
as appropriate for the calling context, but it's not clear how
to handle that for input arguments.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (85
a warning for those options and have make filter the warning out.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
--
Sent via pgsql-hackers
On 11/26/16 12:30 AM, Jim Nasby wrote:
On 11/25/16 6:00 PM, Tom Lane wrote:
OIDs? Then use pg_describe_object() to turn that into text when dumping.
How would I get pg_dump to do that?
I could certainly make this work if there was some way to customize how
pg_dump dumps things, but AFAIK
ding a field without a DEFAULT, adding the DEFAULT after that, and
then slowly updating all the existing rows...
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE
ts of a file into a
field via an INSERT or UPDATE?
I've done that in the past via psql -v var=`cat file`, but there's
obviously some significant drawbacks to that...
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
think the API would work as-is, but I suspect there's other places where
we'd like to be able to have this capability (arrays and JSONB come to
mind).
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in T
;d
probably be possible to round up a few companies to fund it.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
--
Sent via pgsql-hackers mail
't (like safely switch the user the backend is using).
I think there might be other uses as well, since there's several other
places where we need something that's kind-of like a backend, but if
Heikki's work radically shifts the expense of running many thousands of
backends
ppening anytime soon.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To
rnal representation, it seems a bit silly to reinvent that wheel
if we don't need to. Bonus points if it would also throw an error if you
fed it duplicated object keys.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Dat
hat is from one CF to the next.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresq
201 - 300 of 2230 matches
Mail list logo
