e to modify the storage position.
>
IMHO I think display order is very important to users. First, don't
break the select *, no matter how bad it is to code that. Next, don't
break copy or pg_dump/restore. We've fielded a lot of questions on
the ordering of columns for display and simplicity reasons.
The storage order is orthogonal to the display order. display order can be
handled
in attnum and the new storage order can be the new column.
--elein
---(end of broadcast)---
TIP 6: explain analyze is your friend
d of the old
> deprecated abstime. If you're interested, feel free to work on it.
> No one else has taken an interest in a long time.
>
For other recent time travel ideas see:
http://www.varlena.com/GeneralBits/122.php
Time travel is not cheap, though.
--elein
[EMAIL PROT
will. Be careful out there.
elein
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the
On Tue, Feb 13, 2007 at 01:32:11PM -0500, Bruce Momjian wrote:
> Gregory Stark wrote:
> > Alternatively, what does the trailing "a" in varlena signify? Would this be
> > varlenb?
>
> "attribute"
>
> --
Actually varlena stands for &
On Wed, Jan 31, 2007 at 03:41:31PM -0500, Tom Lane wrote:
> elein <[EMAIL PROTECTED]> writes:
> > gcc -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Winline -Wendif-labels
> > -fno-strict-aliasing -g -Wno-error -L../../../../src/port
> > -Wl,-rpath,'/local/pgsq
- Forwarded message from elein <[EMAIL PROTECTED]> -
To: pgsql-general@postgresql.org
Cc: elein <[EMAIL PROTECTED]>
Subject: [GENERAL] 8.2.1 Compiling Error
Mail-Followup-To: pgsql-general@postgresql.org
From: elein <[EMAIL PROTECTED]>
Debian Linux. Have always built
ed for good reason), but I think this might be a
> >more practical method for making the pg_dump logic more easily reusable.
> >
> >
> >
>
> I like this idea. For example, we might usefully map some of this to
> psql \ commands, without having to replicate the
e
> I'll put in a stub about the "queues" stuff and see how people like the
> whole thing.
Have you made any consideration of providing feedback on autovacuum to users?
Right now we don't even know what tables were vacuumed when and what was
reaped. This might actually be
se the extended query protocol
> and don't Sync or wait for a reply until you've sent them all.
>
> regards, tom lane
>
In shell scripts that do things in the database I often put >1 statement
in the line. Since it is the shell, I want quick results. U
with representation, which is the property dealt with by
> I/O functions - their fundamental purpose is to convert between external
> and internal representation.
>
You can fake out the input function by putting a check clause on
the type definition. I agree there should be hooks allowing
input/output functions to be written in pls.
late to the thread, again,
--elein
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
On Fri, Sep 08, 2006 at 05:20:18PM -0400, Tom Lane wrote:
> elein <[EMAIL PROTECTED]> writes:
> > I think what you are saying is that the domain checking (proposed constraint
> > existence checking) would need to be done in more places and I'm not sure I
> >
On Fri, Sep 08, 2006 at 03:47:23PM -0400, Tom Lane wrote:
> elein <[EMAIL PROTECTED]> writes:
> > a) if subtypes/domains can have constraints then the model should
> >not be different for domains only but for all types. Constraint
> >checking would only
>
On Fri, Sep 08, 2006 at 02:33:13PM -0400, Tom Lane wrote:
> elein <[EMAIL PROTECTED]> writes:
> > Domains and subtypes.
>
> >* Create new child type from values in parent type.
> >* Maintain only checks for constraints
> >* Create implicit casts fr
On Thu, Sep 07, 2006 at 07:12:17PM -0700, Josh Berkus wrote:
> Elein,
>
> > I may have missed some stuff here. Obviously. For example how to divide
> > and conquer the various aspects of the issues raised here. But this is a
> > high, high level proposal at this time.
>
. No special type checking for
simple subtypes was necessary.
I may have missed some stuff here. Obviously. For example how to divide and
conquer the various aspects of the issues raised here. But this is a high, high
level proposal at this time.
Comments, volunteers are welcome.
--
Also people trying to download slony have to do some
hunting to find things. The source only tar is not
available on pgfoundry.
one of them,
elein
On Thu, Aug 31, 2006 at 10:33:36AM -0400, Chris Browne wrote:
> What's up there? It has been down all week.
>
> We're trying
hink the direction *in the
long term* should be to allow multiple arguments (as a ROW type?) and other
base or complex types as arguments. The value would be a type itself and
the datatype must do the right thing regarding it. This may not be practical
for short-term
d up. I was reading this as a way to
dump the CONTENTS of a view not the DEFINITION of a view.
I thought someone sneaked in pg_dump of a query in there.
--elein
>
>
> ---(end of broadcast)---
> TIP 6: explain analyze is your fri
s the SQL side. The language itself would have predefined ways
of getting arguments and returning data. I'm not sure if this approach
would work with the bonus extras on plpgsql, but it should.
If anyone wants to pursue this area, please include me on the discussion
and I can try to provide
existing code
> works fine and I can just happily keep additing functionality to both
> analyze.c and tablecmds.c. And it's possible we won't always want to have the
> two match.
>
> Has anyone looked at applying the ADD INHERITS patch yet? Would it
hen again, I like
> to live dangerously and I am not required to attend Java100.
>
> Michael
Overall, I suggest you come to understand more about how open source
projects, and postgresql, specifically work. Discuss with others
*spec
I'll see what I can do about expanding my requirements/test
cases. Casting was not in my original test cases.
What else have I missed? Copy domain gripes to [EMAIL PROTECTED]
--elein
[EMAIL PROTECTED]
On Sat, May 06, 2006 at 10:19:39PM -0400, Tom Lane wrote:
> Bruce Momjian
On Wed, May 03, 2006 at 10:12:28AM -0500, Jim C. Nasby wrote:
> On Tue, May 02, 2006 at 07:45:13PM -0700, elein wrote:
> > On Tue, May 02, 2006 at 12:00:42PM -0500, Jim C. Nasby wrote:
> > > On Mon, May 01, 2006 at 06:43:00PM -0700, elein wrote:
> > > > On Mon, Ma
On Tue, May 02, 2006 at 12:00:42PM -0500, Jim C. Nasby wrote:
> On Mon, May 01, 2006 at 06:43:00PM -0700, elein wrote:
> > On Mon, May 01, 2006 at 07:47:06PM -0400, Tom Lane wrote:
> > > "Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> > > > I think a big
. The majority of the crowd should be able to use SERIAL in
the majority of cases. One reason I am adamant about this is the
v. useful dependencies that are (should be) set between the table
and the sequence when it is declared as a SERIAL.
--elein
>
>
g opinions on that issue.
--elein
On Sat, Apr 29, 2006 at 05:54:19PM -0400, Tom Lane wrote:
> In some recent activity on the patches list about responding to bug #2073,
> http://archives.postgresql.org/pgsql-bugs/2005-11/msg00303.php
> we've been discussing various possible tweaks to
On Mon, Mar 27, 2006 at 11:41:30AM -0500, Tom Lane wrote:
> elein <[EMAIL PROTECTED]> writes:
> > But I like the idea of centralizing the check in the input/output
> > functions. It seems clearer and cleaner.
>
> I remembered the problem with doing it that way: an inp
t checks issues.
But I like the idea of centralizing the check in the input/output
functions. It seems clearer and cleaner. The procedural language
checks are harder, but may be easier to implement if there were
a centralized check domain functionality.
--elein
> --
> Jim C. Nasby,
On Fri, Mar 24, 2006 at 06:27:13PM -0500, Tom Lane wrote:
> elein <[EMAIL PROTECTED]> writes:
> > Operators have the single distinction from functions in that when one
> > argument
> > has an unknown type, then an exact match is tried with the unknown arg
> >
On Fri, Mar 24, 2006 at 08:33:51PM +0100, Peter Eisentraut wrote:
> elein wrote:
> > Domains lay the groundwork for inherited basetypes
> > or subtypes.
>
> Semantically, a domain and a subtype are completely different things. A
> domain restricts the possible valu
On Fri, Mar 24, 2006 at 03:47:13PM -0500, Tom Lane wrote:
> elein <[EMAIL PROTECTED]> writes:
> > Attached is a patch to parse_oper.c which essentially does the
> > following. The major change is in binary_oper_exact().
> > Instead of checking only one level of the
e.
2) Are there any test cases that were not covered by regression
and my tests?
3) Should I add my test case to the regression tests?
4) Eventually this feature should be added to the docs. Should
I wait until all of the pieces are in place or go ahead and
docume
onality of updatable views is substantially different than the use of
> synonyms alone. If/when updatable views are implemented, I wouldn't have a
> problem switching create synonym to actually create a view.
Since updateable views are relatively easy to construct using rules
I&#x
On Thu, Mar 02, 2006 at 08:41:20PM -0500, Tom Lane wrote:
> elein <[EMAIL PROTECTED]> writes:
> > ... What I'm saying is that the opclass needs to be
> > an option to PRIMARY KEY and FOREIGN KEY--
>
> PRIMARY KEY and UNIQUE, you mean.
>
> This was bro
this should be handled.
If FKs will be able to recognize the opclass of the datatype, then the
primary key should also using the same code. But if you can only create
PK constraints on default BTREE opclasses then you can only create FKs on
default BTREE opclasses. What
On Mon, Feb 20, 2006 at 09:03:29AM +0100, Michael Paesold wrote:
> Elein wrote:
> >http://www.varlena.com/GeneralBits/128.php
> >
> >Known Problems and Issues:
> >
> > * Creating the table with an email PRIMARY KEY did not use our
> >comparison functi
On Sun, Feb 19, 2006 at 10:34:02AM -0800, elein wrote:
> On Sun, Feb 19, 2006 at 01:26:31AM -0500, Tom Lane wrote:
> > elein <[EMAIL PROTECTED]> writes:
> > > I've got a domain based on a text type.
> > > I've overridden the equal operator with
> >
On Sun, Feb 19, 2006 at 11:34:21PM +0100, Martijn van Oosterhout wrote:
> On Sun, Feb 19, 2006 at 01:36:41PM -0800, elein wrote:
> > On Sun, Feb 19, 2006 at 10:29:35PM +0100, Martijn van Oosterhout wrote:
> > > On Sun, Feb 19, 2006 at 12:59:35PM -0800, elein wrote:
> > >
On Sun, Feb 19, 2006 at 10:29:35PM +0100, Martijn van Oosterhout wrote:
> On Sun, Feb 19, 2006 at 12:59:35PM -0800, elein wrote:
> > On Sun, Feb 19, 2006 at 07:57:42PM +0100, Martijn van Oosterhout wrote:
> > > ORDER BY x ASC is a synonym for ORDER BY x USING >. That&
On Sun, Feb 19, 2006 at 07:57:42PM +0100, Martijn van Oosterhout wrote:
> On Sun, Feb 19, 2006 at 10:34:02AM -0800, elein wrote:
> > Actually I can do and have done this. It is being tested now.
> > I did create an opclass. It creates a UNIQUE index just fine
> > for the
On Sun, Feb 19, 2006 at 01:26:31AM -0500, Tom Lane wrote:
> elein <[EMAIL PROTECTED]> writes:
> > I've got a domain based on a text type.
> > I've overridden the equal operator with
> > lower(text) = lower(text).
>
> This won't work, you need to mak
.
If this is the way domains really are, I would strongly suggest
expanding create domain to merge with create type (under) and
allow us to list the basic functions.
--elein
[EMAIL PROTECTED]
Example;
--
-- check constraint isemail for email base type
--
create or replace function isemail(tex
pg_hba.conf when these changes
occur.
elein
[EMAIL PROTECTED]
On Sun, Jan 01, 2006 at 01:30:46PM -0500, Tom Lane wrote:
> I was reminded of $subject by
> http://archives.postgresql.org/pgsql-admin/2006-01/msg2.php
>
> While I haven't tried it, I suspect that allowing a DNS host
On Thu, Oct 27, 2005 at 09:12:15PM -0400, Andrew Dunstan wrote:
>
> The docs have this description for pg_class::relfilenode: "Name of the
> on-disk file of this relation; 0 if none". However, Elein just pointed
> out to me that there are no entries with 0, so
pm contained
> >several
> >un-expanded @@PGBINDIR@@ prefixes - once I replaced them with /usr/bin it
> >all
> >ran just fine.
This is also a problem for 64bit machines which like to install
things in lib64. The @@PGBINDIR@@ is also unset in these cases.
Generally a shor
before feature freeze,
> as the recent changes to create PL support functions in pg_catalog
> have made both pg_dump and createlang noticeably uglier than before.
> We could have dispensed with those hacks. Oh well.
>
> Comments?
This idea appears to me to be sound. It
one of the difficulties "in making it possible for OQL
programs to access SQL" data is the inability of object databases to handle
nulls [Melton 95].
Elein
--
[EMAIL PROTECTED]Varlena, LLCwww.varlena.com
a few comments scattered inline...
On Tue, Jun 07, 2005 at 02:53:32PM -0300, Josh Berkus wrote:
> Folks,
>
> I had a lot of time to kill on airplanes recently so I've gone
> digging through /contrib in an effort to sort out what's in
> there and try to apply some consistent rules to it. Before
>
On Thu, May 12, 2005 at 03:30:59PM -0400, Tom Lane wrote:
> [EMAIL PROTECTED] (elein) writes:
> > Also, if you do not trust the newsysview team to develop good views
> > (with input for hackers), how can you possibly expect every dba and tool
> > maker to access the system ca
this.
It would be better to spend time to work on really good system views and
allow people build on them, starting from a higher level than the
system catalogs.
elein
=
[EMAIL PROTECTED]Varlena, LLCwww.varlena.
Adding to the ambiguity is the dot notation used for
composite columns. Don't forget the other end ignoring
those required parens.
is foo.bar.zap
a database.schema.table
a schema.table.column
a table.column.column
--elein
On Wed, May 11, 2005 at 03:21:42PM -0400
and any other small gotchas. A large gotcha might be a reason
to not do it, but I have not seen mention of any.
--elein
[EMAIL PROTECTED]
On Fri, May 06, 2005 at 12:19:12PM -0400, Andrew Sullivan wrote:
> On Fri, May 06, 2005 at 03:37:21PM +1000, Neil Conway wrote:
> >
> > But I
rface
of SQL is also imperative for interfaces that want to
create scripts and/or do operations on the data found
in the system catalog. e.g. drop all foreign keys linked
to table foo.
Elein
[EMAIL PROTECTED]
On Thu, May 05, 2005 at 09:22:40PM -0700, Josh Berkus wrote:
> Tom, Andrew
On Fri, May 06, 2005 at 01:20:09AM -0500, Jim C. Nasby wrote:
> On Fri, May 06, 2005 at 02:43:19AM -, Andrew - Supernews wrote:
> > On 2005-05-06, Christopher Kings-Lynne <[EMAIL PROTECTED]> wrote:
> > >> Hmmm ... we argued about this. I was in favor of hiding the OIDs
> > >> because OIDs are
documented extension that lives in the same place
> (INFORMATION_SCHEMA) so that we know where to look to find it.
This is the bulk of what we are working on. Some is duplicated
work with the information schema but it usually has more information
or context.
--elein
[EMAIL PROTECTED]
>
>
Usability is a feature we don't put enough emphasis on, ever.
New system views would help people be more productive with
PostgreSQL, enable new interfaces to have better packaged information
and help all of the people required to support a Postgre
On Sat, Apr 30, 2005 at 05:31:28PM -0400, Tom Lane wrote:
> [EMAIL PROTECTED] (elein) writes:
> > On Sat, Apr 30, 2005 at 04:17:59PM -0400, Tom Lane wrote:
> >> It is trivial to crash 8.0's record_out
> >> by lying to it about the rowtype of its first argument.
>
On Sat, Apr 30, 2005 at 04:17:59PM -0400, Tom Lane wrote:
> An example that Elein put up yesterday:
> http://archives.postgresql.org/pgsql-general/2005-04/msg01384.php
> caused me to realize that type output functions that depend on
> additional arguments to determine what they are
If it is ok with you, I'll review these for a General Bits article
and then link them up at varlena.com/GeneralBits/Tidbits
with some of the other talks I've collected.
--elein
On Fri, Apr 22, 2005 at 06:33:49PM +1000, Neil Conway wrote:
> A few hours ago, I gave a talk at linux.c
suggest putting it on the bug list to fold into
the replacement arguement marshalling code. That way
we won't (ideally) forget the intended behaviour and
may even fix it at some point.
--elein
On Sat, Apr 16, 2005 at 03:39:55PM -0400, Tom Lane wrote:
> [EMAIL PROTECTED] (elein) writes:
>
Are you saying that the code was supposed "unflatten" the
arguments of a function into a possible composite type taking into
consideration the possible inheritance information of the
composite type?
elein
On Fri, Apr 15, 2005 at 08:04:36PM -0400, Tom Lane wrote:
> In parse_fun
I use df to see what functions are available. I want to see them all.
--elein
On Fri, Apr 01, 2005 at 12:59:43PM +0800, Christopher Kings-Lynne wrote:
> >Uh, who exactly agreed to that? I know when I do \df it's generally
> >to check out built-in functions not my own. I don
You specify the inheritance on the creation of the child table.
See CREATE TABLE
--elein
On Wed, Feb 16, 2005 at 11:48:54PM +0300, Oleg Bartunov wrote:
> Hi there,
>
> is't possible to make table to be inherited from another table in case
> both tables already exist. I tried
table
inheritance.
--elein
[EMAIL PROTECTED]
On Wed, Feb 16, 2005 at 07:22:39AM -0800, Eliot Simcoe wrote:
> Hello everyone,
>
> I'm working on a project which makes extensive use of the PostgreSQL table
> inheritance features and am interested in fixing some bugs I have come
written in a trusted/untrusted language.
--elein
On Tue, Feb 08, 2005 at 11:12:07PM +0100, Thomas Hallgren wrote:
> Hi,
> A TRUSTED language specifies that ordinary users can use the language.
> It also implies that access to the file system should be prevented. In
> essence, ordinary use
able and goes ideally quickly once through.
--elein
[EMAIL PROTECTED]
INFO: vacuuming "public.NCA_log_head"
INFO: index "NCA_log_head_pkey" now contains 2795382 row versions in 8178 pages
DETAIL: 0 index row versions were removed.
83 index pages have be
They probaly released the informix database patents.
This is pertinent to us as several of them were interesting
implementations of things like the function manager.
--elein
On Tue, Jan 11, 2005 at 08:04:48AM -0800, Darcy Buskermolen wrote:
> IBM has just announced they are waving all rig
rt delete rules. We'll see how it goes.
This was suggested over on irc.
Thank you...More news as it happens.
--elein
On Sun, Dec 05, 2004 at 06:02:00PM -0500, Tom Lane wrote:
> elein <[EMAIL PROTECTED]> writes:
> > Also, what are the reasons for forbidding triggers on views?
&
the reasons for forbidding triggers on views?
It is to prevent *possible* mayhem or will it cause real problems?
Thanks,
elein
- End forwarded message -
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
Isn't there a load/unload function for the .so that would work
in this case?
--elein
On Wed, Nov 10, 2004 at 12:11:27PM -0500, Tom Lane wrote:
> John Hansen <[EMAIL PROTECTED]> writes:
> > When doing CREATE or REPLACE FUNCTION of a builtin function, it seems to
> > ha
This is the kind of thing I can usually help with.
However, right now I'm a little swamped with customer work.
I can back someone up, though.
--elein
On Mon, Aug 09, 2004 at 06:28:33PM -0400, Bruce Momjian wrote:
> Marc G. Fournier wrote:
> > On Mon, 9 Aug 2004, Jos
Double postings are a PITB
- Forwarded message from elein <[EMAIL PROTECTED]> -
Date: Thu, 22 Jul 2004 21:31:37 -0700
From: elein <[EMAIL PROTECTED]>
To: Robert Treat <[EMAIL PROTECTED]>
Cc: Joe Conway <[EMAIL PROTECTED]>,
elein <[EMAIL PROTECTED]>,
that the usefulness
of our implementation is limited and so the documentation
should focus on other areas.
elein
On Thu, Jul 22, 2004 at 03:21:04PM -0700, David Fetter wrote:
> Kind people,
>
> I am writing a document patch for the tutorials section, and would
> like to change th
configure as necessary.
--elein
On Mon, Jul 12, 2004 at 05:27:23PM -0400, Tom Lane wrote:
> "Merlin Moncure" <[EMAIL PROTECTED]> writes:
> > IMO, forcing su password at initdb time (allowing blank password with a
> > very stern warning) and bumping localhost to
ly true in reality?
Obviously these comments are not for 7.5 nor are they
make or break issues.
--elein
On Sun, Jul 11, 2004 at 11:17:19AM -0400, Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > On Sat, Jul 10, 2004 at 09:18:28PM -0700, elein wrote:
> >> The
implementation both techniques
would be possible since returning the array
is kind of cool ;-)
--elein
[EMAIL PROTECTED]Varlena, LLCwww.varlena.com
PostgreSQL Consulting, Support & Training
PostgreSQL General
FYI: I'm agreeing w/Tom who is agreeing with me.
The tag change should be good. I do hope people are
not relying on seeing COMMIT when the transaction
rolled back. It does not seem that in this case
they would.
elein
On Sat, Jul 10, 2004 at 04:13:49PM -0400, Tom Lane wrote:
> Bruce
While Alvarro, et al are messing with transaction syntax
this would be a good time to clarify this message.
--elein
On Fri, Jul 09, 2004 at 10:16:29AM -0400, Bruce Momjian wrote:
>
> Do we want to add this to TODO:
>
> * Issue an extra message when COMMIT completes a failed
rt on #postgresql.
--elein
On Mon, Jul 05, 2004 at 12:28:32PM -0400, Andrew Dunstan wrote:
>
>
> Tom Lane wrote:
>
> >Andrew Dunstan <[EMAIL PROTECTED]> writes:
> >
> >
> >>Can anyone suggest why I might be seeing this effect (each notice comes
The README.spi said that $rv->{rows} should return the number of
rows affected for INSERT, UPDATE & DELETE. It seems to return NULL.
@{$rv->{rows}} also returns NULL.
-- drop table users ( email text, who text );
create table users ( email text, who text );
insert into users values ('[EMAIL PRO
--
-- An SQL error causes subsequent function creation of an otherwise
-- healthy function to fail WHEN RUN with:
--ERROR: creation of function failed:
--(in cleanup) Undefined subroutine &PLPerl::mksafefunc called at (eval 4) line 4.
--
-- Workaround is to close and reopen the connection
Good reason. Now I'm excited. I'll download and run
tests and try to do a write up in general bits next week.
cheers,
elein
On Sat, Jun 05, 2004 at 05:00:24PM -0400, Tom Lane wrote:
> I wrote:
> > regression=# insert into bar values (row(row(1.1, 2.2), row(3.3, 4.4)));
&g
dcast)---
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
--elein
[EMAIL PROTECTED]Varlena, LLCw
It is the SQL2003 standard for (update else insert).
Check out General Bits monday... :-)
--elein
[EMAIL PROTECTED]Varlena, LLCwww.varlena.com
PostgreSQL Consulting, Support & Training
PostgreSQL Gen
Can we add the MERGE command to the TODO list?
Is anyone actively examining this issue?
And yes, I realize it is not for 7.5.
It would be good to be able to say it is on
the list for some future release, however.
Thanks,
elein
[EMAIL
Bcc:
Subject: Adding MERGE to the TODO list
Reply-To:
Can we add the MERGE command to the TODO list?
Is anyone actively examining this issue?
And yes, I realize it is not for 7.5.
It would be good to be able to say it is on
the list for some future release, however.
Thanks,
elein
he goal is publication on General Bits and techdocs.
There is also the possibility of publishing a version in
other more marketing oriented venues.
Contact me if you are interested in working on this
or have work you are willing to share on this.
elein
PS: Sorry for the cro
ct the headers if that is what is
necessary.
All advice is greatly appreciated.
Thanks,
elein
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
st feature which enables people to track
the status of their issues.
But as it is now, a resident python person would be extremely
helpful to wrap up any customization (yes we'll want customization).
--elein
[EMAIL PROTECTED]
On Fri, Feb 27, 2004 at 03:31:14PM -0800, Josh Berkus wrote:
> Mik
nt to text.
elein
On Fri, Feb 20, 2004 at 11:33:39AM -0500, Tom Lane wrote:
> Robert Treat <[EMAIL PROTECTED]> writes:
> > so ISTM that your example is certainly a deficiency if not a bug.
>
> I believe it is a bug or at least an unimplemented feature in plpgsql:
> plpgs
Right. Sorry. My brain was over on parameter issues and
I did not reread my original bug...
On Fri, Feb 20, 2004 at 01:03:08PM -0500, Tom Lane wrote:
> elein <[EMAIL PROTECTED]> writes:
> > Shouldn't all function calls go (through fast path or fmgr
> > or the language
. However, I suspect
that there is no underlying support for
type checks in the general system.
Elein
- Forwarded message from elein <[EMAIL PROTECTED]> -
I can create a function with a domain and
define it to return a domain.
The parameter is checked to see if it qualifies
I agree with Tom on this. Good operator combinations
are hard to find when you are creating new operators.
=> is a particularly good one.
Barring any override from the SQL200x standard,
I would strongly suggest AS, too.
elein
[EMAIL PROTECTED]
On Sun, Jan 25, 2004 at 02:54:12PM -0500, Tom L
I did not get any response to this question on
general so I am forwarding it to hackers.
Thanks,
elein
- Forwarded message from elein <[EMAIL PROTECTED]> -
Date: Sat, 29 Nov 2003 14:11:20 -0800
From: elein <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: elein <[EMAIL PROT
opriate. My audience might not be core
hackers, but getting the larger user group to participate as well
as prepare for conversion is something I can help promote.
(Just contact me to submit articles for publication--the invitation
is always open.)
--elein
==
What is the status of CVS head? Isn't it in sync
with 7.4.RC2? I just upgraded from CVS and rebuilt
clean and initdb now gives this lovely informative
initdb failed message.
I haven't had trouble previously with cvs head or
other versions.
$ sudo make install
...
PostgreSQL installation comple
emeritus is a perfectly good latin word. No need to
dumb things down.
--elein
On Wed, Nov 05, 2003 at 05:26:29PM -0500, Bruce Momjian wrote:
> Tom Lane wrote:
> > Josh Berkus <[EMAIL PROTECTED]> writes:
> > > B) What contributors are listed under Major Developers who h
note format. But maybe there is some
clarification text you can use.
http://cookie.varlena.com:8080/varlena/GeneralBits/48.php
elein
On Thu, Oct 30, 2003 at 11:59:05PM -0500, Bruce Momjian wrote:
>
> OK, I have committed changes to release.sgml so most complex entries
> have a paragraph
The key value of having both SD vs. GB is scope.
We *do* want to be able to have dictionaries with
scope that is function specific,
statement specific and global (available to all functions).
I do use plpython primarily for running aggregates.
Having the different scopes (if they all worked
corr
If the function is defined with ANY*
and you defer typing the arguments until the first reference
then I think you will get what you want with the CASE statement.
If the function is called if( x>y, x+1, y), the first reference
is in the argument list and so should be typed there. But if
you pas
1 - 100 of 119 matches
Mail list logo
