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.
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
29 matches
Mail list logo
