as I've heard there is precisely zero demand for.
We have a customer that wants to use it as part of a MySQL-to-Postgres
migration.
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation | fax: 732.331.1301
499 Thornall Street, 2nd Floor | [EMAIL PROTECTED]
Edison, NJ
On Jan 28, 2008 8:21 AM, Gokulakannan Somasundaram [EMAIL PROTECTED] wrote:
I am not seeing my mail getting listed in the archives. So i am just
resending it, in case the above one has got missed.
It was sent. Archive processing is delayed.
--
Jonah H. Harris, Sr. Software Architect | phone
, but seeing how late we are in the 8.3 release
cycle, I thought I'd better post it for comment anyway.
+1
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation| fax: 732.331.1301
499 Thornall Street, 2nd Floor | [EMAIL PROTECTED
back here if you'd like. Or, you can
fix it. It's up to you :)
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation| fax: 732.331.1301
499 Thornall Street, 2nd Floor | [EMAIL PROTECTED]
Edison, NJ 08837| http
, that i won't repeat the stated
mistakes again.
The Missing of Thick Keyword - i don't know how it got removed.
Thanks,
Gokul
On Jan 23, 2008 10:49 PM, Jonah H. Harris [EMAIL PROTECTED] wrote:
On Jan 23, 2008 11:28 AM, Gokulakannan Somasundaram [EMAIL PROTECTED]
wrote:
Fixed a type
On Jan 15, 2008 5:04 AM, Neil Conway [EMAIL PROTECTED] wrote:
Any thoughts whether to apply or not?
Seems like a much more sane approach to me -- +1.
Agreed, sounds and looks better to me. +1
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation
On Nov 28, 2007 3:53 PM, Tom Lane [EMAIL PROTECTED] wrote:
Entirely removing the example of how to do it with rules doesn't
seem like a good idea.
Agreed.
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation| fax: 732.331.1301
499 Thornall
) NOT NULL,
PRIMARY KEY (test_id));
ALTER TABLE test_tbl ALTER COLUMN test_name TYPE VARCHAR(64);
I can't find any case where this doesn't work... but perhaps you guys
know of some.
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation| fax
what's the point of comparing attbyval etc when
you've already checked it's the same type OID.
True.
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation| fax: 732.331.1301
33 Wood Ave S, 2nd Floor| [EMAIL PROTECTED]
Iselin, New Jersey
not without
exposing any implementation details outside the type.
Seems like too much work for a fairly simple use-case.
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation| fax: 732.331.1301
33 Wood Ave S, 2nd Floor| [EMAIL PROTECTED]
Iselin, New
On 9/1/06, Tom Lane [EMAIL PROTECTED] wrote:
Attached is a draft patch that makes rules support RETURNING ...
What format is that patch in? Either something's wrong or Gmail just
went really wacko.
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation
For
Tom Lane - Against
Jonah Harris - For
David Fetter - For
Josh Drake - Against
Andrew Dunstan - Against
Josh Berkus - For
Dave Page - For
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation| fax: 732.331.1301
33 Wood Ave S, 2nd Floor| [EMAIL
On 8/25/06, Bruce Momjian [EMAIL PROTECTED] wrote:
Sorry, we did not get enough feedback to include this in 8.2. Please
add it to pgfoundry and let's see how it goes.
Yep... it's too bad. A new feature no other database has now goes to
it's final resting place on pgfoundry.
--
Jonah H
to pick it up.
Of course, I may always be wrong. Perhaps pgfoundry is more popular
than I've seen in past experience. Maybe one of the core developers
does want to pick up full disjunctions for 8.3.
Guess we'll just have to wait and see...
--
Jonah H. Harris, Software Architect | phone
advertise we have full text indexing.
Wherever it ends up, I look forward to seeing the promotion and
announcements. Tzahi has put a lot of work into it over the past few
months.
I'm done on this topic but would gladly appreciate public or private
proof regarding pgfoundry's popularity.
--
Jonah H
On 8/26/06, Andrew Dunstan [EMAIL PROTECTED] wrote:
So, yes, it is used, and by far more that just hard core hackers.
OK. Kewl. I just hadn't run into many people (except hackers) that
knew about it. Thanks for sharing that.
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
On 8/5/06, Tom Lane [EMAIL PROTECTED] wrote:
Jonah H. Harris [EMAIL PROTECTED] writes:
Here's the updated patch with DELETE RETURNING removed. This isn't
really an issue because no one wanted DELETE RETURNING to begin with.
I don't have the time to add DELETE RETURNING back in. My initial
On 8/9/06, Tom Lane [EMAIL PROTECTED] wrote:
UPDATE tries to place the new tuple on the same page it's already
on.
I think he meant for INSERT.
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation| fax: 732.331.1301
33 Wood Ave S, 2nd Floor
way, but now is the time to
decide.
I don't care either way, RETURNS is fine I guess.
OK, but we need a final version soon.
Sure thing.
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation| fax: 732.331.1301
33 Wood Ave S, 2nd Floor
.
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation| fax: 732.331.1301
33 Wood Ave S, 2nd Floor| [EMAIL PROTECTED]
Iselin, New Jersey 08830| http://www.enterprisedb.com/
pg82-iuret-073106.patch
Description: Binary data
this?
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation| fax: 732.331.1301
33 Wood Ave S, 2nd Floor| [EMAIL PROTECTED]
Iselin, New Jersey 08830| http://www.enterprisedb.com/
---(end of broadcast
On 6/6/06, Jonah H. Harris [EMAIL PROTECTED] wrote:
On 6/6/06, ITAGAKI Takahiro [EMAIL PROTECTED] wrote:
This is a patch for table/index fillfactor control discussed in
http://archives.postgresql.org/pgsql-hackers/2006-06/msg00175.php
There's 4 shift/reduce conflicts which I believe
UNION.
Maybe if we thought a little bit larger we could clean up all of that
messiness at one stroke.
Have you had any ideas on how to best accomplish this?
--
Jonah H. Harris, Database Internals Architect
EnterpriseDB Corporation
732.331.1324
---(end of broadcast
On 4/3/06, Mark Wong [EMAIL PROTECTED] wrote:
Once I get a test system going again in the lab I'll start
posting some data. I'm planning a combination of
block sizes (BLCKSZ and XLOG_BLCKSZ) and number
of WAL buffers.
Cool. I'm looking forward to the results.
--
Jonah H. Harris, Database
On 3/14/06, Andrew Dunstan [EMAIL PROTECTED] wrote:
Maybe one of the proponents could put together a comparison matrix ofhow this is done in each of the databases previously mentioned.
Hans,
I don't have time to do this, would you like to take a stab at it?
-- Jonah H. Harris, Database Internals
consistent with other lookups.
This is correct, for a synonym to be added, the cost for 1 synonym
would be the same as adding 1 more table/function/view/etc depending on
the catalog you're searching; I don't think it's too costly. I'm
going to start a new thread to propose this clearly.
-- Jonah H. Harris
Adams). The worst-case scenario
would be an additional search only if an object weren't found in a
catalog search, basically this would be the cost of using synonyms and
wouldn't affect performance for everyone else. Oracle does have a
small cost only when using synonyms as well.
-- Jonah H. Harris
from Oracle's way of doing it if it makes sense.
-- Jonah H. Harris, Database Internals ArchitectEnterpriseDB Corporation732.331.1324
for the record, this is lacking pg_dump support as well asdocumentation.
True.
I'd be glad to submit my patch and/or cleanup this one if its something the community would be willing to accept.-- Jonah H. Harris, Database Internals ArchitectEnterpriseDB Corporation732.331.1324
On 3/7/06, Hans-Jürgen Schönig [EMAIL PROTECTED] wrote:
we should definitely work together.what is the status of your patch?maybe we can discuss this off list?
The last time I worked on it was on 8.0 (I think), but it wouldn't take
much to get it up to speed on 8.2. It's actually very similar to
. Some users don't have the ability to choose how
vendors/developers write their software and they can't easily just
convert an entire application to use search_path where they once had
synonyms (especially if the application is fairly sizable).
-- Jonah H. Harris, Database Internals
in Oracle; synonyms do have other purposes outside of this single one listed.
-- Jonah H. Harris, Database Internals ArchitectEnterpriseDB Corporation732.331.1324
schemas.
-- Jonah H. Harris, Database Internals ArchitectEnterpriseDB Corporation732.331.1324
On 3/2/06, Jonah H. Harris [EMAIL PROTECTED] wrote:
On 3/2/06, Tom Lane [EMAIL PROTECTED]
wrote:
Jonah H. Harris [EMAIL PROTECTED] writes: INSERT/UPDATE/DELETE seem to work fine in normal operation but there is an
error with DELETE RETURNING when used through PL/pgSQL.
Probably other places
is %', current_rec.test_id;
RAISE NOTICE 'test_name is %', current_rec.test_name;
RETURN;
END;
$$ LANGUAGE plpgsql;-- Jonah H. Harris, Database Internals ArchitectEnterpriseDB Corporation732.331.1324
diff -cr pgsql/src/backend/access/common/printtup.c pgsql-iudret/src/backend/access/common/printtup.c
*** pgsql/src
On 3/2/06, Tom Lane [EMAIL PROTECTED] wrote:
Jonah H. Harris [EMAIL PROTECTED] writes: INSERT/UPDATE/DELETE seem to work fine in normal operation but there is an error with DELETE RETURNING when used through PL/pgSQL.
Probably other places too.I don't see any provision here for ensuringthat
36 matches
Mail list logo
