structures could be kept, but maybe
it'd also be possible to plan only that part of the join tree where the
params are used in a scan/join qual.
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
replan' decision. The only
comparable numbers invariant to system load are the planners costs (not
in ms but unitless) and maybe actual number of processed tuples, but
never actual ms.
Regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
for the sphere
- so poi on earth can be compared to another, but not a poi on earth
with a poi on the moon. ?
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
or function that returns it though.
Regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Teodor Sigaev wrote:
I found something strange with merge join. Let there are two table
Sorry, postgresql's version is 8.4 from today CVS
For what it's worth - 8.4.0 gives as expected.
aap=# explain UPDATE
t1
SET
f1 = t1.f1 || t2.f1
FROM
t2
WHERE
t2.f1 = t1.f1 AND
t2.f2 =
number of iterations it is possible to have decent call statistics
/ parameter distributions. Maybe the the parameter value distribution
could even be annotated with actual cached plans.
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
Hello list,
I'm wondering if there would be community support for adding using the
execute message with a rownum 0 in the c libpq client library, as it
is used by the jdbc driver with setFetchSize.
kind regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers
Mark Mielke wrote:
On 02/26/2010 03:11 PM, Yeb Havinga wrote:
Or instead of letting users give the distribution, gather it
automatically in some plan statistics catalog? I suspect in most
applications queries stay the same for months and maybe years, so
after some number of iterations
Takahiro Itagaki wrote:
Yeb Havinga yebhavi...@gmail.com wrote
I'm wondering if there would be community support for adding using the
execute message with a rownum 0 in the c libpq client library, as it
is used by the jdbc driver with setFetchSize.
The setFetchSize for libpq
here there could be an improvement.
- it might even be possible to 'test' plans during low-usage hours
bad:
- unknown how big space for cached plans should be
- if big cached plan space doesn't fit in memory, actual planning
probably better than fetching from disk, ~= 5 to 10ms.
regards,
Yeb
be valuable for postgres on the fact alone that
it is almost twice as fast, and probably easy to integrate and unit
test. We make heavy use of the numeric data type, so I'm very interested!
regards
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
Pavel Stehule wrote:
2010/3/3 Yeb Havinga yebhavi...@gmail.com:
Theo Schlossnagle wrote:
I didn't look deeply at the postgres internals to see if there was a way
to do double - numeric and integer-types - numeric without intermediary
string format. If that sort of thing is easy
it hard to diagnose without getting to the debugger.
I don't know if the buildfarm machines fail on initdb, however I think
that maybe a better errormessage at that point in initdb could help
future users.
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
Pavel Stehule wrote:
Hello
this patch contains a string formatting function format
Hi Pavel,
This is supercool. Haven't tried it out yet but surely will, thanks!
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
Robert Haas wrote:
On Fri, Feb 26, 2010 at 3:28 PM, Yeb Havinga yebhavi...@gmail.com wrote:
I'm wondering if there would be community support for adding using the
execute message with a rownum 0 in the c libpq client library, as it is
used by the jdbc driver with setFetchSize
Tom Lane wrote:
Yeb Havinga yebhavi...@gmail.com writes:
What if the default operation of e.g. php using libpq would be as
follows: set some default fetchsize (e.g. 1000 rows), then just issue
getrow. In the php pg handling, a function like getnextrow would wait
for the first pgresult
: this is not a patch to HEAD but a local version, so line numbers are
off, patch supplied for discussion purposes only.
kind regards,
Yeb Havinga
diff --git a/src/backend/commands/explain.c b/src/backend/commands/explain.c
index 56d9c5b..454d59b 100644
--- a/src/backend/commands/explain.c
+++ b/src/backend
why someone might not want to use libpq still seems like a
good idea.
...Robert
Hello Robert,
Thank you for your support, but am unsure if it is wise to put time in
it due to the other reactions.
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
by
search_indexed_tlist_for_var and it seems like correct behaviour, see
stack trace below.
I'm unsure what is a good approach to solve this problem: let
get_variable not give an error in this case?
regards,
Yeb Havinga
#0 search_indexed_tlist_for_var (var=0xe32dc0, itlist=0xe67290,
newvarno=65001, rtoffset=0
and testexpr.
Other info: there are now only appends to the context-buf. The problems
with OUTER var I mentioned earlier are gone now arguments are deparsed
using get_rule_expr instead of deparse_expression.
regards,
Yeb Havinga
diff --git a/src/backend/utils/adt/ruleutils.c
b/src/backend/utils/adt
as the javascript null.
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
of that type. In PostgreSQL terms, this could perhaps
mean that by 'tagging' a datatype as a lineair order, it could
automatically have a range type defined on it, like done for the array
types currently.
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers
Robert Haas wrote:
On Fri, Apr 9, 2010 at 10:33 AM, Robert Haas robertmh...@gmail.com wrote:
On Fri, Apr 9, 2010 at 7:55 AM, Yeb Havinga yebhavi...@gmail.com wrote:
Robert Haas wrote:
Under the first type [4pm,5pm) =
[4pm,4:59:59pm], while under the second [4pm,5pm) = [4pm,4
and for the latter, what would the
increment be.. OTOH is a range of integers with increment x a different
type from range of integers with increment y, if xy? Maybe the
increment step and continuous/discrete could be typmods.
regards
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers
Robert Haas wrote:
On Fri, Apr 9, 2010 at 11:07 AM, Yeb Havinga yebhavi...@gmail.com wrote:
.. I now see the example of different ranges in your original mail with
different unit increments. Making that more general so there could be
continuous and discrete ranges and for the latter, what
= '1m');
The problem with mixing units with ranges is that units are properties
of some underlying datatype but not all types on which ranges can be
defined.
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
need certain kinds of properties of the operator involved, e.g.
being commutative, transitive etc? Else the join reordering fails. The
latter fails for the overlap operator.
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
Robert Haas wrote:
On Sat, Apr 10, 2010 at 12:05 PM, Yeb Havinga yebhavi...@gmail.com wrote:
Jeff Davis wrote:
To give some context, I started a thread a while ago:
http://archives.postgresql.org/pgsql-hackers/2009-10/msg01403.php
Interesting, a join type for overlaps, which
The patch I sent earlier is flaud with respect to subplan parameter
numbering, I counted from zero where the parParam list had to be used.
Yeb Havinga wrote:
See patch below against HEAD.
Example of query against catalog:
postgres=# explain verbose select oid::int + 1,(select oid from
) or a
message to the user that their report is currently unavailable and they
should retry in a few minutes.
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
lose track about whether this is
about fsync or full_page_writes and did not get on the track again)
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
/kohonen),
so my local filters could make labels based on that, instead of perhaps
badly spelled keywords in subjects or message body.
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
=ENGLISHEToolsDocumentSource.safeSearch=false
I wonder if a cluster algorithm could tag articles with (multiple)
keywords, e.g. 'hackers','prepared transaction','dba' etc etc. I could
then make filters or ranking on: hackers AND optimizer - +10.
regards,
Yeb Havinga
--
Sent via pgsql-hackers
Marc G. Fournier wrote:
On Fri, 14 May 2010, Yeb Havinga wrote:
Marc G. Fournier wrote:
On Thu, 13 May 2010, Alvaro Herrera wrote:
Excerpts from Yeb Havinga's message of jue may 13 15:06:53 -0400 2010:
My $0.02 - I like the whole 'don't sort, search' (or how did they
call
it?) just let
.
The GBs of data are gathered at the site of the libpq client (pgresult
object gathered/allocated while consuming result input from backend).
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
standby servers went south.
(under the assumption that async servers are mostly on too slow links to
consider for sync standby).
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
The linux kernel also uses it when it's availabe, see e.g.
http://tomoyo.sourceforge.jp/cgi-bin/lxr/source/arch/x86/crypto/crc32c-intel.c
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
tree traversal removed
At some point read reading http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43556
Changing versions to gcc 4.4.3-4ubuntu5 and binutils 2.20.1-3ubuntu5
made the strange segfaults go away.
I don't know which versions I had installed when having the segfault, sorry.
regards,
Yeb
Joshua D. Drake wrote:
On Fri, 2010-07-09 at 16:57 +0200, Yeb Havinga wrote:
Hello list,
Due to dependency requirements my development machine has ubuntu
repositories jaunty, lucid and intrepid.
I would not expect anything to work in an environment that is that
misconfigured. I
On Fri, Jul 9, 2010 at 10:18 PM, Robert Haas robertmh...@gmail.com wrote:
On Fri, Jul 9, 2010 at 4:10 PM, Yeb Havinga yebhavi...@gmail.com wrote:
Joshua D. Drake wrote:
On Fri, 2010-07-09 at 16:57 +0200, Yeb Havinga wrote:
Hello list,
Due to dependency requirements my development
Tom Lane wrote:
The reason I'm on about this at the moment is that I think I see how to
get ruleutils to print PARAM_EXEC Params as the referenced expression
rather than $N ...
Wouldn't this obfuscate the plan more than printing subplan arguments at
the call site?
regards,
Yeb Havinga
Tom Lane wrote:
Yeb Havinga yebhavi...@gmail.com writes:
Tom Lane wrote:
The reason I'm on about this at the moment is that I think I see how to
get ruleutils to print PARAM_EXEC Params as the referenced expression
rather than $N ...
Wouldn't this obfuscate the plan more than
.
In my head the neuron for 'principle component analysis' went on while
reading this. Back in college it was used to prepare input data before
feeding it into a neural network. Maybe ideas from PCA could be helpful?
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers
, that
were executed as expected. Regression test still ok.
Attach is a new patch with all things described above addressed.
regards,
Yeb Havinga
Robert Haas wrote:
On Mon, Mar 29, 2010 at 4:21 AM, Joachim Wieland j...@mcknight.de wrote:
On Mon, Mar 29, 2010 at 12:32 AM, Robert Haas robertmh
Robert Haas wrote:
On Wed, Jul 14, 2010 at 7:27 AM, Yeb Havinga yebhavi...@gmail.com wrote:
Attach is a new patch with all things described above addressed.
Thanks!
I think we should probably hold off applying this until some of the
other KNNGIST work is ready, or we have some other
Böszörményi disagrees and supplies a new version of this patch.
Depending on a reaction of Zoltán Böszörményi I think patch (A) should
be set to either Returned With Feedback, if a new version is in the
making, or Rejected if not.
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list
sync (or not) and for sync
standbys the replication_mode specified.
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
. It would be great if ideas from
both patches could be merged into one.
regards,
Yeb Havinga
Patch A: Zoltán Böszörményi
Patch B: Fujii Masao
* Is the patch in context diff format?
A: Yes
B: Yes
* Does it apply cleanly to the current CVS HEAD?
A: No
B: Yes
* Does it include reasonable tests
that automates setup, a few transactions and failures would benefit
everyone working and testing on replication.
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
)
4 - replication modes recv, fsync and replay bot not async
5 - Zoltan's strict_sync_replication parameter
Just an idea, what about
for 4: acknowledge_commit = {no|recv|fsync|replay}
then 3 = yes, if acknowledge_commit != no
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql
reaching quorum).
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
|replay}
instead of
replication_mode = {async|recv|fsync|replay}
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
looks a bit like the synchronous_replication = N # similar in
name to synchronous_commit Simon Riggs proposed in
http://archives.postgresql.org/pgsql-hackers/2010-05/msg01418.php
regards,
Yeb Havinga
PS: Please bear with me, I thought a bit about a way to make clear what
deduction users must
in the documentation and how they
would be reflected with the standby related parameters.
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
returns !MyWalSnd-sndrqst. That value is initialized to false in
that procedure and it cannot be changed to true during execution of that
procedure, or can it?
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
at
CreateCheckPoint(), EndPrepare(), FlushBuffer(),
RecordTransactionAbortPrepared(), RecordTransactionCommit(),
RecordTransactionCommitPrepared(), RelationTruncate(),
SlruPhysicalWritePage(), write_relmap_file(), WriteTruncateXlogRec(),
and xact_redo_commit().
regards,
Yeb Havinga
--
Sent via pgsql-hackers
received word from Zoltan
that work on a new patch is planned. It would be great if ideas from
both patches could be merged into one.
regards,
Yeb Havinga
Patch A: Zoltán Böszörményi
Patch B: Fujii Masao
* Is the patch in context diff format?
A: Yes
B: Yes
* Does it apply cleanly to the current
I've received word from Zoltan
that work on a new patch is planned. It would be great if ideas from
both patches could be merged into one.
regards,
Yeb Havinga
Patch A: Zoltán Böszörményi
Patch B: Fujii Masao
* Is the patch in context diff format?
A: Yes
B: Yes
* Does it apply cleanly
.
Wouldn't it be relatively easy, to rewrite the filter expression by
adding expressions, instead of replacing constants, in the disjunctive
case, so the example at hand would become:
WHERE (d1.ID=234409763) or (d2.ID=234409763)
AND (d2.BasedOnID=234409763) or (d2.ID=234409763)
regards,
Yeb
Robert Haas wrote:
On Wed, Jul 28, 2010 at 7:24 AM, Yeb Havinga yebhavi...@gmail.com wrote:
Sorry? I though what Equivalence Class provides is the proving that
using this qualification or another will *not* affect the output.
In a query like...
SELECT d1.ID, d2.ID
FROM
.
Our (more than one line) patch was explicitly designed to walk from a
specific parent to a child exactly once. It passes regression tests.
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
*/,
maybe the recursion could be stopped there as well, i.e. not only
setting inhcount to 1, but actually adding the child relation one time
to the wqueue.
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
Yeb Havinga wrote:
Robert Haas wrote:
This still leaves open the question of what to do about the similar
case involving attributes:
That problem looks significantly more difficult to solve, though.
I'm looking at ATPrepAddColumn right now, where there is actually some
comments about
though that once the definitions could be the same on all
servers, having them in a system catalog would be a good thing. However
that'd propably hard to setup, and also in the case of failures during
change of the parameters it could become very messy.
regards,
Yeb Havinga
--
Sent via pgsql
are
done in a memory context soon to be deleted (PortalHeapMemory). It
passes regression as well as the script below.
regards,
Yeb Havinga
DROP SCHEMA IF EXISTS test_inheritance CASCADE;
CREATE SCHEMA test_inheritance;
SET search_path TO test_inheritance;
CREATE TABLE top (i int);
CREATE TABLE
Robert Haas wrote:
On Mon, Aug 2, 2010 at 9:20 AM, Yeb Havinga yebhavi...@gmail.com wrote:
The attached patch uses the globally defined list.
I can't speak for any other committer, but personally I'm prepared to
reject out of hand any solution involving a global variable. This
code is none
are pretty much zero. :-)
Me too, now I understand the fixes must be in the execution stages.
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Robert Haas wrote:
On Mon, Aug 2, 2010 at 2:56 PM, Yeb Havinga yebhavi...@gmail.com wrote:
Hence the ATOneLevelRecursion routing is usable in its
current form for all callers during the prep stage, and not only
ATPrepAddColumn.
Well, only if they happen to want the visit each table only once
Yeb Havinga wrote:
The underlying cause is the failure of the code to recognize that if
relation C inherits from both A and B, where A and B both have column
x, that A.x 'is the same as' B.x, where the 'is the same as' relation
is the same that holds for (A.x, C.x) and (B.x, C.x), which
Robert Haas wrote:
On Tue, Aug 3, 2010 at 3:05 PM, Yeb Havinga yebhavi...@gmail.com wrote:
Yeb Havinga wrote:
The underlying cause is the failure of the code to recognize that if
relation C inherits from both A and B, where A and B both have column x,
that A.x 'is the same as' B.x
Robert Haas wrote:
On Wed, Aug 4, 2010 at 3:48 AM, Yeb Havinga yebhavi...@gmail.com wrote:
I just read that thread. In the beginning there is a short discussion what
the non-astonishing behaviour of the RENAME in the case of multiple origin
inheritance should be, which is preventing renames
Robert Haas wrote:
On Wed, Aug 4, 2010 at 6:41 AM, Yeb Havinga yebhavi...@gmail.com wrote:
If child inherits column A from parent1 and parent2, and it is then
renamed to B in parent2, what should the name be in the child after
the rename is completed?
The column should be renamed
violate any
definition of inheritance. After all: all conditions regarding
inheritance I can think of are valid *after* the DDL update.
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
Tom Lane wrote:
Yeb Havinga yebhavi...@gmail.com writes:
A.a_columnB.a_column
| /
v v
C.a_column
C inherits from A and B.
Well, if A and B inherited the column from a common ancestor, he can
easily do that. If not, maybe he should have thought harder
Daniel Oliveira wrote:
There is a way to acess a index inside a c function without using a
sql statement ?
Yes, if you know the oid of the index you want to scan, you can use
functions from backend/access/index/indexam.c.
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql
This message is probably in the top 10 of 2010's most insignificant
messages, but:
_outPlannedStmt does not write the bool field transientPlan and it is
not accompanied by the comment /* NB: this isn't a complete set of
fields */ that exist at other places.
regards,
Yeb Havinga
, instead of having to build
one in the user defined functions gist functions for every datatype.
Any thoughts?
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
translate on a russion page about gist in the
search for information. Besides that also reading Guttmans r-tree paper
was good, to have any idea what picksplit, penalty and union are
supposed to do.
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
On 2012-01-13 21:14, Frederico wrote:
Hi folks.
Is there any restriction in create and start threads inside Postgres?
I'm trying to develop a multithread planner, and some times is raised a
exception of access memory.
I'm debugging the code to see if is a bug in the planner, but until now, I
. This would also be
useful in conjunction with a connection pooler. This would still allow
the option to prevent a back transition to non-default client labels.
--
Yeb Havinga
http://www.mgrid.net/
Mastering Medical Data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
to make
that fail.
But the idea is that if that different value is a (possibly changed into
a new) allowed default value, a RESET to that new default value will be
allowed, by definition, because it is a default value.
--
Yeb Havinga
http://www.mgrid.net/
Mastering Medical Data
--
Sent via pgsql
repeatable client_label switches.
However, single-directed domain transition from bigger-privileges to
smaller-privileged domain by users' operation is also supported on
operating system, and useful feature to restrict applications capability
at beginning of the session.
--
Yeb Havinga
http
On 2012-02-20 06:37, Don Baccus wrote:
On Feb 19, 2012, at 7:24 PM, Tom Lane wrote:
It's not clear to me whether pure/leakproof functions are meant to be a
strict subset of immutable functions
Superset, not subset, unless my guessing is wrong. How could pure be a subset of
immutable?
If
Policy version: 24
Policy from config file:targeted
--
Yeb Havinga
http://www.mgrid.net/
Mastering Medical Data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Fedora 16 to run it?
--
Yeb Havinga
http://www.mgrid.net/
Mastering Medical Data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
-a -S targeted -s unconfined_u -r s0-s0:c0.c1023 mgrid
the regression tests pass :-)
test label... ok
test dml ... ok
test create ... ok
test misc ... ok
I'll continue reviewing the patch.
--
Yeb Havinga
http
On 2012-02-24 15:17, Yeb Havinga wrote:
I don't know what's fishy about the mgrid user and root that causes
c0.c1023 to be absent.
more info:
In shells started in a x environment under Xvnc, id -Z shows the
system_u and c0.c1023 absent.
In shells started from the ssh daemon, the id -Z
and then list_delete on pointer of that listcell?
Some comments contain typos, I can spend some time on this, though I'm
not a native english speaker so it won't be perfect.
regards,
Yeb Havinga
--
Yeb Havinga
http://www.mgrid.net/
Mastering Medical Data
--
Sent via pgsql-hackers mailing list (pgsql
On 2012-02-27 12:49, Asif Rehman wrote:
Hi Yeb Havinga,
I was digging archives to see anyone worked on supporting domain's
over composite type and found your patch, but that was pulled back.
According to commitfest comments it needs some more work...
There were some issues with using
On 2012-02-24 17:25, Yeb Havinga wrote:
On 2012-02-23 12:17, Kohei KaiGai wrote:
2012/2/20 Yeb Havingayebhavi...@gmail.com:
On 2012-02-05 10:09, Kohei KaiGai wrote:
The attached part-1 patch moves related routines from hooks.c to
label.c
because of references to static variables. The part-2
appends to
the list, always. That the list is reset on transaction commit/abort
time, is done and also already documented elsewhere. A new reader could
be confused to not find transaction related things in
sepgsql_set_client_label().
regards,
Yeb
--
Yeb Havinga
http://www.mgrid.net/
Mastering
in
sepgsql-regtest.te and to describe the actual feature.
I can probably write some docs tomorrow.
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
and setting the
client label can be avoided by denying changing the client label with
sepgsql_setcon() from a trusted procedure, which would also make some sense:
ERROR: cannot override the client label of a trusted procedure during
execution.
--
Yeb Havinga
http://www.mgrid.net/
Mastering Medical
. Maybe this could be a leftover from
the initial implementation as GUC variable?
- earlier I suggested preventing setting a new client label from a
trusted procedure, however I just read in the original post that this
was how the current usecase of Joshua is set up. Suggestion withdrawn.
--
Yeb
On 2012-03-11 11:33, Yeb Havinga wrote:
On 2012-03-10 10:39, I wrote:
I can probably write some docs tomorrow.
Attached is v5 of the patch, with is exactly equal to v4 but with
added documentation.
s/literalcube(1) == '(1)'/literal// in that patch please
--
Sent via pgsql-hackers
unwanted results, like the ones currently seen?
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
of a trusted procedure)
+as mandated by the system.
--
Yeb Havinga
http://www.mgrid.net/
Mastering Medical Data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
When building a minimal PostgreSQL under the latest mingw (2018),
make check will give a few dozen fails with the server exiting on code
2. The build is fine when -O2 is removed from the CFLAGS. This behaviour
is present on all revs on the REL9_1_STABLE branch that I tested, among
which
be deduced. I wouldn't be
surprized if storing implicatures like this would reduce the size to O(n).
regards,
Yeb Havinga
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
and CTEScan appear in EXPLAIN output, it would be
nice to have a meaningful hit when looking for the term in the
documentation page, instead of 'Your search for *cte* returned no hits.'
regards,
Yeb Havinga
1 - 100 of 240 matches
Mail list logo
