of the wCTE, even if no actual insertions occurred.
Unless I have missed anything, I think all other issues have been
adequately addressed. Since there are no red lights, I shall proceed. :)
Best regards,
Matt
On Sat, Jun 17, 2017 at 9:55 PM, Peter Geoghegan <p...@bowt.ie> wrote:
> On Sat, Jun 17, 2017 at 7:49 AM, Matt Pulver <mpul...@unitytechgroup.com>
> wrote:
> > With the proposed "INSERT ... ON CONFLICT () SELECT" feature, the
> > get_or_create_id() functi
ned, even
with exclusion constraints.
Feedback/guidance is most welcome.
Best regards,
Matt
ast
likely to cause people serious issues. As for the other options, consider
me opposed.
- Matt K.
by not getting Windows licenses for your DR
environment, you are far better off just saving one more license and making
both your production and DR server be Linux builds.
- Matt K.
3/gin-indexing-array-of-enums.html
cheers
andrew
Thanks,
Matt
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
it belongs to Trip
because I wrote it on company time. Let me see if I can open source a
version of it later this week that way you can use it for testing.
- Matt K.
be at QUEUE_HEAD. I prepared a second patch
that splits asyncQueueReadAllNotifications. Exec_ListPreCommit then only calls
the worker version only when needed. This avoids the duplicate lock.
Thanks,
Matt Newelldiff --git a/src/backend/commands/async.c b/src/backend/commands/async.c
index 91ba
On Monday, September 28, 2015 07:22:26 PM Tom Lane wrote:
> Matt Newell <newe...@blur.com> writes:
> > 1. When a connection issues it's first LISTEN command, in
> > Exec_ListenPreCommit QUEUE_BACKEND_POS(MyBackendId) = QUEUE_TAIL;
> > this causes the connection to i
On Tuesday, September 29, 2015 09:58:35 PM Tom Lane wrote:
> Matt Newell <newe...@blur.com> writes:
> > On Monday, September 28, 2015 07:22:26 PM Tom Lane wrote:
> >> Possibly. sinval catchup notification works like that, so you could
> >> maybe
> >> inve
d most
likely end up staying very small. If the backend local list does grow too
large then the connection could be killed or handled in some other appropriate
way.
I am happy to attempt coming up with a patch if the ideas are deemed
worthwhile.
Thanks,
Matt Newell
--
Sent via p
Even if it does fit in memory I suspect memory bandwidth is more important
than clock cycles.
http://people.freebsd.org/~lstewart/articles/cpumemory.pdf
This paper is old but the ratios should still be pretty accurate. Main
memory is 240 clock cycles away and L1d is only 3. If the
should
help to smooth out that noise and show a clearer picture.
However, I'm happy with the committed version. Thanks Tom.
- Matt K.
On Thu, Feb 19, 2015 at 9:40 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Matt Kelly mkell...@gmail.com writes:
Attached is the fixed version. (hopefully
of the global stats struct.
- Matt K.
On Thu, Jan 29, 2015 at 6:49 PM, Jim Nasby jim.na...@bluetreble.com wrote:
On 1/28/15 11:18 PM, Matt Kelly wrote:
In a previous thread Tom Lane said:
(I'm also wondering if it'd make sense to expose the stats timestamp
as a callable function, so
This is now: https://commitfest.postgresql.org/4/128/
On Thu, Jan 29, 2015 at 7:01 PM, Matt Kelly mkell...@gmail.com wrote:
Robert, I'll add it to the commitfest.
Jim, I'm not sure I understand what you mean? This new function follows
the same conventions as everything else in the file
to expose that value
to SQL. It shouldn't impact anything else in the server.
I'm not particularly attached to the function name, but I didn't have a
better idea.
The patch should apply cleanly to master.
- Matt K
pg_stat_snapshot_timestamp_v1.patch
Description: Binary data
--
Sent via pgsql
, as well as helping to smooth
graphs of the statistics that are based on highly granular snapshotting.
- Matt Kelly
these two things
together. Its probably worth it to make these two separate discussions and
separate patches.
- Matt Kelly
*Just sanity checking myself: Shutting down the server, applying the
different patch, 'make clean install' in postgres_fdw, and then restarting
the server should obviously
just like work_mem.
Obviously, this shouldn't block your current patch but its worth revisiting.
- Matt Kelly
the guarantee that a PGquery
won't be reused twice in a row should be sufficient, and the only alternative
is
to add a unique id, but that will add further complexity that I don't think is
warranted.
Feedback is very welcome and appreciated.
Thanks,
Matt Newell
diff --git a/doc/src/sgml/libpq.sgml b
unnecessary complexity and might also make
it easy for users to never retrieve and free some results.
There are probably plenty of other wrinkly bits to think about.
Yup, I'm sure i'm still missing some significant things at this point...
Matt Newell
/*
* src/test/examples/testlibpqpipeline2
On Thursday, December 04, 2014 04:30:27 PM Claudio Freire wrote:
On Thu, Dec 4, 2014 at 4:11 PM, Matt Newell newe...@blur.com wrote:
With the API i am proposing, only 2 new functions (PQgetFirstQuery,
PQgetLastQuery) are required to be able to match each result to the query
that caused
provide a function to do
just that as a convenience to the user, if it's going to be a common use-case.
It would be no different than how PQexec processes and discards results.
Matt
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
)
checkResult(conn,result,curQuery,PGRES_FATAL_ERROR);
if (curQuery == query3)
checkResult(conn,result,curQuery,PGRES_TUPLES_OK);
}
Note that the curQuery == queryX check will work no matter how many results a
query produces.
Matt Newell
--
Sent via
instead of a sync per PQsendQuery will be needed. That could make things
tricky though with multi-statement queries, because currently the only way to
detect when results change from one query to the next are a ReadyForQuery
message.
Matt Newell
/*
* src/test/examples/testlibpqpipeline.c
On Jun 24, 2014, at 9:42 AM, Tom Lane t...@sss.pgh.pa.us wrote:
I think this means we can write off VAX on NetBSD/OpenBSD as a viable
platform for Postgres :-(. I'm sad to hear it, but certainly have
not got the cycles personally to prevent it.
Why? NetBSD/vax has supported shared
I honestly do not mean any offence, just out of curiosity.
If you guys care about money and time why would you spend the best years of
your life basically copying commercial products for free?
1) For the same reasons commercial vendors build competing products: different
tools in the same
--- On Mon, 12/28/09, Andres Freund and...@anarazel.de wrote:
From: Andres Freund and...@anarazel.de
Subject: Re: [HACKERS] parse tree to XML format
To: pgsql-hackers@postgresql.org
Cc: Robert Haas robertmh...@gmail.com, matt nuc...@yahoo.com
Date: Monday, December 28, 2009, 7:39 PM
Is there some way to export the postgresql query parse tree in XML format? I
can not locate the API/Tool etc to do that...
thanks
-Matt
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
the
postmaster / postgres components?
Thanks for any pointers,
Matt
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Aug 11, 1:11 pm, j...@agliodbs.com (Josh Berkus) wrote:
Is there an easier way of going about this other than replacing the
postmaster / postgres components?
I'd start with creating my own extended version to psql (the client
library), I suppose. But since I don't really know what kind
adding an anyelement2 pseudotype ... The context was a
compatibility SQL function to support Oracle's DECODE function.
The reason it's not in there already is we didn't seem to have quite
enough use-case to justify it. Do you have more?
No. Even this case, for me, is more an expedient
A few months ago at
http://archives.postgresql.org/pgsql-general/2006-11/msg01770.php the
notion of adding an anyelement2 pseudotype was discussed. The context
was a compatibility SQL function to support Oracle's DECODE function.
Assuming this new pseudotype has not been added yet, I'm ready to
When I apply pgcluster-1.7.0rc1-patch to Postgres REL8_2_STABLE I get
a handful of rejects.
The patch applies to the 8.2.0 tarball without rejects and without
fuzz. That's good. Now on to some fun with pgcluster...
However, the patch will not apply to cvs branch REL8_2_0. This all
raises
difference between REL8_2_STABLE, REL8_2_0
STABLE doesn't mean static. It's the branch for what will be the
8.1.x series.
Okay, and this is all different from HEAD, which will presumably become
8.3, correct?
---(end of broadcast)---
TIP 9: In
The [pgcluster-1.7.0rc1-patch] patch applies to the 8.2.0 tarball ...
However, the patch will not apply to cvs branch REL8_2_0.
I've been told that the pgcluster patch patches some generated files
(parse.h and other apparently).
Yes, I could not at first apply to REL8_2_0 because the patch
Can't keywords share code
the way to do what you want I think is
like this:
foo: bar_or_baz
{ code block }
;
bar_or_baz: bar | baz ;
I'll try that, thanks.
---(end of broadcast)---
TIP 6: explain analyze is your friend
I suggest you to contribute this kind of code to orafce project [1]
Thanks, I'll go play over there for a while.
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
I found it interesting that gram.c and parse.h already supported SYSDATE.
Only after you ran bison ;-). They're derived files.
Well, so much for my conspiracy theory.
Thanks for the bison lesson.
---(end of broadcast)---
TIP 7: You can help
Why should we add this Oraclism to PostgreSQL? I doesn't add any new
feature.
Certainly, this feature falls well within the class of completely
gratuitous proprietary extensions that we typically reject.
I now agree completely. My purpose is to migrate Oracle databases to
Posgres, and I
Redirecting from -general.
I'd like SYSDATE to work syntactically and semantically the same as
CURRENT_TIMESTAMP
current_time and the like are hardcoded in the grammar. You'd have to
do the same for sysdate.
Okay, I patched. The patch follows. Please comment. In particular,
I've just
head does this to me when I try to initdb:
[EMAIL PROTECTED]:~$ /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
The files belonging to this database system will be owned by user postgres.
This user must also own the server process.
The database cluster will be initialized with locale
head does this to me when I try to initdb:
I bet you didn't do a full recompile after cvs update.
If you're not using --enable-depend then you really have
to do make clean or even make distclean.
I am using --enable-depend, but I'll make clean and give
it another shot.
head does this to me when I try to initdb:
...
do make clean or even make distclean.
I am using --enable-depend, but I'll make clean and give
it another shot.
All better. Thanks.
I guess I be suspicious of --enable-depend for a while.
---(end of
head does this to me when I try to initdb:
I bet you didn't do a full recompile after cvs update.
If you're not using --enable-depend then you really have
to do make clean or even make distclean.
I am using --enable-depend, but I'll 'make clean' and give
it another shot.
changing much else.
Matt
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
of the current
inheritance design.
'Tis a hard problem :-(
I think that's why i'm interested:) I hope that I can succeed so as to not
have wasted your valuable time.
BTW, i'm on the list now, so no need to cc me.
Matt
---(end of broadcast)---
TIP 1
The system cannot find the path specified.
Try cd /D c:/Test
The /D option changes the current directory *and* the current drive in one
command.
--
Matt Emmerton
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire
On Tue, 2005-08-30 at 00:56 +0200, Martijn van Oosterhout wrote:
I saw the discussion about an tester for MVCC. Since I'd never done
anything with asyncronous queries before, I figured I'd try to write
something useful with it. The result is at:
http://svana.org/kleptog/pgsql/mvcctest.tar.gz
Rewriting all my Oracle code function-by-function could be painful
...
I'm still trying to hold on to my fantasy that I can hack Postgres (and
contrib/ora2pg) into submission.
Why don't you just use EnterpriseDB?
I looked at EnterpriseDB a few months ago. The installation errored.
It
On Fri, 2005-09-02 at 12:29 -0700, Josh Berkus wrote:
still trying to hold on to my fantasy that I can hack Postgres (and
contrib/ora2pg) into submission.
I'm happy to work with you on ora2pg
Cool.
It looks like I should have referred to contrib/oracle, not
contrib/ora2pg, but you got my
doc/src/sgml/storage.sgml says:
The last 2 bytes of the page header,
structfieldpd_pagesize_version/structfield, store both the page size
and a version indicator. Beginning with
productnamePostgreSQL/productname 8.0 the version number is 2;
productnamePostgreSQL/productname 7.3 and 7.4 used
On Thu, 2005-09-01 at 18:28 -0400, Tom Lane wrote:
Matt Miller [EMAIL PROTECTED] writes:
Basically I'd like my Pl/pgSQL code to be able to utilize the try/catch
paradigm of error handling without the overhead of subtransactions
[Pl/pgSQL] can't even do 2+2 without
calling the main
On Wed, 2005-08-31 at 13:13 -0500, Tony Caduto wrote:
the function below also raises no errors at create, but at run time it does.
...
CREATE or REPLACE FUNCTION public.test_func9(out firstname varchar,out
lastname varchar)
RETURNS SETOF pg_catalog.record AS
$BODY$
Declare
row record44;
On Wed, 2005-08-31 at 11:59 -0700, Josh Berkus wrote:
If a table does not exist, we don't want to check for that and bounce
the function; possibly the function will only be called in a context
where the table does exist.
The Pl/pgSQL compiler should be able to dive into SQL statements, hit
the
On Wed, 2005-08-31 at 15:29 -0400, Tom Lane wrote:
Matt Miller [EMAIL PROTECTED] writes:
I don't remember the last time I intended to write code that referenced
something that did not exist in the database.
Almost every day, people try to write stuff like
CREATE TEMP TABLE foo
On Fri, 2005-08-26 at 13:13 -0400, Nicholas Walker wrote:
You can't use savepoints, you can trap errors which is implemented using
savepoints. You still might want to write code like this:
BEGIN
SAVEPOINT foo;
IF SOME_ERROR_CODE = 1234 THEN
ROLLBACK TO SAVEPOINT
On Thu, 2005-08-25 at 15:50 +0900, Michael Glaesemann wrote:
* %Remove CREATE CONSTRAINT TRIGGER
Do we really want to remove it,
Also, I believe CONSTRAINT TRIGGERS are the only way to provide
transaction level (rather than statement level) referential
integrity.
Don't deferrable
On Mon, 2005-08-08 at 16:59 -0400, Tom Lane wrote:
Matt Miller [EMAIL PROTECTED] writes:
I want to write some regression tests that confirm the behavior of
multiple connections simultaneously going at the same tables/rows. Is
there something like this already, e.g. in src/test/regress
What we really need is a test program that can issue a command on one
connection (perhaps waiting for it to finish, perhaps not) and then
issue other commands on other connections, all according to a script.
It seems to me that this is what contrib/dblink could allow, but when I
presented that
Perhaps we should look at Expect or something similar.
Where can I get more info on Expect?
I think I found it:
http://expect.nist.gov/
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
On Wed, 2005-08-10 at 16:41 -0400, Tom Lane wrote:
Matt Miller [EMAIL PROTECTED] writes:
It seems to me that contrib/dblink could greatly simplify the design and
coding of multi-user regression tests.
I doubt it would be very useful, since
a script based on that still doesn't let you
On Mon, 2005-08-08 at 16:59 -0400, Tom Lane wrote:
Matt Miller [EMAIL PROTECTED] writes:
I want to write some regression tests that confirm the behavior of
multiple connections simultaneously going at the same tables/rows. Is
there something like this already, e.g. in src/test/regress
.
--
Matt Emmerton
---(end of broadcast)---
TIP 6: explain analyze is your friend
the discussed rewrite of plpgsql by splitting the effort.
That's my two one hundreths of a euro, anyway.
Matt
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
access to columns
in any syntax at all. A simple yes or no would do :)
Matt
BTW: here's the original post adding the rec.(3) syntax to the TODO:
http://archives.postgresql.org/pgsql-hackers/2003-07/msg00425.php
here's someone else who tried something very similar:
http://archives.postgresql.org/pgsql
to
require a rather complete overhaul of plpgsql :-(. But it needs one
anyway.
Look forward to seeing it.
Matt
---(end of broadcast)---
TIP 8: explain analyze is your friend
that, as you say.
OK, download is done. I've got some more general ideas which relate to
this. I'll post along with updated version.
Matt
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs
?) and
marking them as dynamic.
Does that make any sense? Is it worth the work? Or should we just tell
anyone who actually needs it (I don't, at present) 'use another PL'?
Regards,
Matt
diff -u src.orig/pl_comp.c src/pl_comp.c
--- src.orig/pl_comp.c 2004-11-22 10:20:24.0 +
+++ src
, and ideally one guaranteed available (or easily
installable without other dependencies) on every postgres db out there.
That's pretty much why I wrote the patch: to add the one missing feature
I need to write my generic triggers in plpgsql.
Regards,
Matt
---(end
to a trigger
would make writing generic triggers a whole lot easier. And going back
through the archives on this list I see I'm not alone.
Regards,
Matt
On Thu, 2004-11-18 at 13:18, Matt wrote:
Hi,
I got extremely frustrated with having to create a temp table every time
I wanted to access
newbie can cut-and-paste
their way to a halfarsed solution in a (rather long) night!
Regards,
Matt
diff -u src/pl_comp.c src.mk/pl_comp.c
--- src/pl_comp.c 2004-09-13 21:09:20.0 +0100
+++ src.mk/pl_comp.c 2004-11-18 12:59:25.825372489 +
@@ -3,7 +3,7 @@
* procedural language
:(
Hrm the best made plans and all that...
Matt
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
[EMAIL PROTECTED] (Ned Lilly) wrote in message news:[EMAIL PROTECTED]...
Jonathan,
This is exactly how my company has built a very robust ERP application. See
www.openmfg.com.
Hi Mr. Lilly:
I not sure who to address this question to at your company.
I'm a valued added reseller who
74 matches
Mail list logo
