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
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
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
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
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,
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/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/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
;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/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
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
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.
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
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
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/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
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
;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
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
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
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
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
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
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
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
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
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
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
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
'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
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
.
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
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-
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
/ 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
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
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
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!
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&#
| 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
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
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
check constraints easier to
read, and easier to write without backwards boolean logic.
Rather than this, I think an exclusive-or operator would be a lot more
useful. The only difficulty I run into with CHECK constaints is when I
want to ensure that only ONE condition is true.
--
Jim Nasby
On 4/1/16 1:08 PM, Tom Lane wrote:
Jim Nasby writes:
Rather than this, I think an exclusive-or operator would be a lot more
useful. The only difficulty I run into with CHECK constaints is when I
want to ensure that only ONE condition is true.
"bool != bool" works as XOR. I
y wanted to put some effort into this, it would be
possible to better handle filling up a single filesystem that has both
data and WAL by slowly shrinking the VM/FSM to make room in the WAL for
vacuum records. ISTM that's a much more common problem people run into
than filling up a separate
nically difficult to make it "just work"?
Actually, after looking at the code for interval_lt, all that needs to
happen to add this support is to expose interval_cmp_internal() as a
strict function. It already does exactly what you want.
--
Jim Nasby, Data Architect, Blue Treble C
t the info into the archives
might be enough.
I think a code comment pointing at the archived message would be good
though...
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://Blue
r DDL generation capabilities
in the database, but I think the right way to do that is to create the
pg_dump library and then wrap that as a (version-specific) extension.
That way you could loan the pg_dump-9.5 extension in a 9.3 database if
you wanted.
--
Jim Nasby, Data Architect, Blue Treble Consu
rsistent
changes to settings." What would be a non-persistent change? SET LOCAL?
(This is another case where it'd be good if we decided on specific
terminology and referenced the definition from the page.)
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Expe
define a C structure that has the expected members, and an
initializer function that will properly set everything up when you
create a new instance. There's no messing around with the rest of the
guts of python.
*Even more important, everything you need to know about the type is
contained in
-wrap still works correctly. (Might be worth testing mxid wrap too...)
--
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) mobile: 512-569-9461
ere's a lot of folks out there that will never understand enough to
design tests meant to expose data corruption but who could easily code
someone else's design, especially if we provided tools/ways to tweak a
cluster to make testing easier/faster (such as artificially advancing
ly, for an option this obscure, I agree. I don't think we'd want
any normally used stuff named so glibly, but I sure as heck could have
used some easter-eggs like this when I was doing training.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, D
On 5/10/16 11:42 PM, Jim Nasby wrote:
On 5/6/16 4:55 PM, Peter Geoghegan wrote:
On Fri, May 6, 2016 at 2:49 PM, Andres Freund wrote:
Jeff Janes has done astounding work in these matters. (I don't think
we credit him enough for that.)
+many.
Agreed. I'm a huge fan of what Jef
cantly reduce the need for manual review. I think it's a much
better approach to take a methodical approach of writing tests to help
verify a feature works than just randomly banging on it.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture a
.
As for transforms, I suspect we're going to end up with some of those in
initdb in the future, because it's currently the only way you can
improve existing type transformations without breaking existing PL code.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Expert
. This way all the prettiness enhancements could be
contained in a single function w/o the need for generalized interface
used in many places.
+1. I've found the output functions of json.dumps to be very handy.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Expert
first.
One other consideration is cut-over time. Swapping logical master and
replica can happen nearly instantly, while pg_upgrade needs some kind of
outage window.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Tr
.1, etc.
And +1 for ditching major.major.minor in favor of major.minor.0. It's
high time we stop this silliness.
IMHO the beginning of parallelism that we have now is more than enough
to justify 10.0, but that consideration pales compared to fixing the
version numbering system itself.
--
Jim Na
on.
Tom, were you around when sequences were added? I'm guessing that that
was done in response to OIDs becoming a serious problem in user tables
on larger installs; ISTM this is just the next iteration of them being a
problem. (And I suspect the one after this will be pg_attribute or maybe
verhead on ingestion.
Possibly because JSONB silently eats duplicated keys while JSON doesn't
(though in that case even casting to JSONB is probably not what you want).
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in
ch means you've lost your original
type information when you use it. I don't think you could actually do
anything useful here because of that.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in
only the first), do you think that
it will simplify implementation and make it more feature complete?
I think you'll need to be a bit more specific to elicit a response. What
exactly are you proposing to change?
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Anal
that will make it very easy
to accidentally change from one type to the other without meaning to.
--
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
itioning.
I also disagree about PK:PK FK's between a bunch of completely
independent tables being a good way to model this stuff. It doubles the
complexity of every query against a child table and doesn't perform
nearly as well, because your data locality goes down the tubes.
--
J
, we need to be doing *more* of this kind of work, not
less. Lack of support for OO paradigms was one of the drivers for NoSQL.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTrebl
On 5/23/16 4:19 AM, Craig Ringer wrote:
+Batching less useful when information from one operation is required by the
SB "Batching is less useful".
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Troub
urprise me that people would want to parallel dump
from a replica...
--
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) mobile: 512-569-9461
-
On 5/23/16 4:45 PM, David G. Johnston wrote:
On Mon, May 23, 2016 at 5:38 PM, Jim Nasby mailto:jim.na...@bluetreble.com>>wrote:
On 5/23/16 11:55 AM, Peter van Hardenberg wrote:
Fortunately, this seems quite easy to resolve by taking
advantage of our
ability
dy know exactly how
to fail over.
--
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) mobile: 512-569-9461
--
Sent via pgsql-hackers mailing list
; that simply evaluate a boolean expression (and don't
require defining a function).
--
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) mobile:
LL bitmap
implementation).
Related to this, Tom has mentioned in the past that perhaps we should
support abstract use of the [] construct. Currently point finds a way to
make use of [], but I think that's actually coded into the grammar.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin
#x27;ve moved from being
an RDBMS to being a "Data Platform". Improving our OO capabilities just
continues that.
--
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.co
ain for *any*
operations are most welcome! I think allowing queued backgrounded
processes would be a huge win there. If we had real stored procedures
(IE: ability to control transaction state) and a modest background
scheduler then it wouldn't be hard to build that.
--
Jim Nasby, Data Archi
ving a SRF that would
return that info...
As it relates back to this thread the desired "merging" ends up being done
inside this view and at least gives the DBA a central location (well, along
with pg_db_role_setting) to go and look at the configuration landscape for
the system.
I think the goal is good, but the interface needs to be rethought.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
than this version as well as performing better.
I see you dropped multi-dimension support, but I think that's fine.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresq
My thought is that would result in one worker mostly being
responsible for advancing the index scan itself while the other workers were
issuing (and waiting on) heap IO. So even if this doesn't turn out to be a win
for seqscan, there's other places we might well want to use it.
--
Jim Nasby
return a boolean. The performance of that would presumably suck with anything
but a C function, but we could provide some C functions to handle simple cases.
That said, I think the best idea at this stage is either log everything or
nothing. We can always expand upon that later.
--
Jim Nasby, D
exception should not be handled by PLpgSQL handler -- like CANCEL
exception
+1
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscrip
On 1/20/15 9:01 PM, Stephen Frost wrote:
* Jim Nasby (jim.na...@bluetreble.com) wrote:
>+1. In particular I'm very concerned with the idea of doing this via roles,
because that would make it trivial for any superuser to disable auditing. The only
good option I could see to provide t
On 1/21/15 5:38 PM, Stephen Frost wrote:
* Jim Nasby (jim.na...@bluetreble.com) wrote:
On 1/20/15 9:01 PM, Stephen Frost wrote:
* Jim Nasby (jim.na...@bluetreble.com) wrote:
+1. In particular I'm very concerned with the idea of doing this via roles,
because that would make it trivial fo
d be useful to have a separate view that shows all occurrences
of a setting. I recall some comment about source_file and source_line not
always being correct in pg_settings; if that's true we should fix that.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Tre
if XLogHintBitIsNeeded is false? That would be the case if we're not wall
logging hints *on the standby*.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To mak
an entire
database locally, but to then put it's entire contents into WAL? Blech.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your sub
o we could generate wal that's shipped to standby's? That
would allow doing this as part of the formal upgrade process without the need
for preliminary steps.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
--
Sent via pgsql-
nough. For example, what happens if you
CREATE ROLE su SUPERUSER NOINHERIT NOLOGIN;
CREATE ROLE su_role IN ROLE su NOLOGIN;
GRANT su_role TO bob;
and have
su_role:*:*
Does bob get audited all the time then? Only when he does SET ROLE su? For that
matter, how does SET ROLE affect auditing?
--
Ji
hell script instead of directly modifying things itself? Or
perhaps some custom "command file" that could then be replayed by pg_upgrade on
another server? Of course, that's assuming that replicas are compatible enough with
masters for that to work...
--
Jim Nasby, Data Architect, Blu
, 4 and 8 workers make no
difference, then suddenly 16 cuts times by 1/2 to 1/3? Then 32 cuts time by
another 1/2 to 1/3?
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
--
Sent via pgsql-hackers mailing list (pgsql-hack
t ADAT will error if a backup is running, but allow the user to over-ride
that.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
escribing above. We'd have to somehow cover
that same scenario on replicas too.
Perhaps there isn't really an issue here; I suspect ADAT is very rarely used.
What I'm worried about though is that someone is using it regularly for some
reason, with non-trivial databases, and this is
;m starting to feel like this needs a wiki page to get the design pulled
together.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Also, what about:
foreach a,b in '{{{1,2},{3,4}},{{5,6},{7,8}}}'::int[] ?
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your sub
).
Or maybe I'm missing something...
Wasn't the idea that the parent table in a partitioned table wouldn't actually
have a heap of it's own? If there's no heap there can't be an index.
That said, I think this is premature optimization that could be done later.
--
J
would be a function, but
maybe it'd be better to just do this per-subtransaction.
I do agree that this needs to work across the board, not just for plpgsql.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
--
Sent via pgsql-hacke
needs to be very
restrictive. Really, it should be more (or differently) restrictive than SU, so
that you can effectively audit your superusers with minimal worries about
superusers tampering with auditing.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! ht
|disable_asserts. I
have no string idea.
The option would be nice, but I don't think it's strictly necessary. The big
thing is being able to control this on a per-function basis (which I think you
can do with ALTER FUNCTION SET?)
--
Jim Nasby, Data Architect, Blue Treble
xScans have one worker reading the
index and another worker taking index tuples and reading heap tuples...
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
code?
You should remove the array_length() from the last array_offsets test; I don't
see that it buys anything.
I think there should be tests for what happens when you feed these functions a
multi-dimensional array.
Other than that, looks good.
--
Jim Nasby, Data Architect, Blue T
hat to Bruce also, but it's not clear why that
would be any different from an rsync --size-only in the end, presuming
everything went according to plan.
Yeah, if everything is shut down maybe we're OK.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble
to 2, then that pointer should be invalid by the time the pin
count goes from 2 to 1...
I'm worried that a simple test when pin count is 0 could miss some cases of
pointers just happening to be cleared by a second part of the code even though
the pin count has already dropped.
--
Jim N
1401 - 1500 of 2230 matches
Mail list logo
