Ross and Chris,
I was reading too fast :-)
The problem is actually more complex:
We have to distinguish 4 cases when Query could returns zero result:
1. normal - there are no such words
2. query consists of stop-words only
3. query consists of lexems of non-indexed clasess (specified in parser c
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> What does -f do?
> There is concern that using pg_resetxlog by accident could cause
> problems, so it will prompt the user for confirmation by default. -f
> (force) disables that confirmation.
pg_resetxlog already has an -f switch, and I do not think
"Matthew T. O'Connor" <[EMAIL PROTECTED]> writes:
> I have gotten as far as having a vacuum daemon created on postmaster startup.
> It's just a fork from the postmaster, cribbed mostly from the stat collector
> code.
This will not get you very far, because the stat collector is not a real
backe
> Would it be useful to implement the SET SCHEMA command from SQL92? (I
> assume it's also in 99.)
>
> I guess that SET SCHEMA should change the front of the search path, so
> that it would change the schema reported by current_schema(). It would
> be a simplified form of SET SEARCH_PATH.
Hrm -
Barry Lind <[EMAIL PROTECTED]> writes:
> You can no long insert large values into a bigint column without a
> cast.
This seems to be fallout from the move to tighten up implicit coercions
(cf http://archives.postgresql.org/pgsql-hackers/2002-04/msg00528.php
as well as lots of earlier discussions
Would it be useful to implement the SET SCHEMA command from SQL92? (I
assume it's also in 99.)
I guess that SET SCHEMA should change the front of the search path, so
that it would change the schema reported by current_schema(). It would
be a simplified form of SET SEARCH_PATH.
--
Oliver Elph
I have added the names of the people who have the power to complete each
item. It may not be the original author.
---
P O S T G R E S Q L
7 . 3 O P E NI T E M S
Neil Conway wrote:
> Scott Shattuck <[EMAIL PROTECTED]> writes:
> > Allow DBA/Database Owner to log in even when max_connections has
> > been reached so they can determine which queries are hung via
> > pg_stat_activity etc. and perform any other needed work to restore
> > stability.
>
> Allowing
Your patch has been added to the PostgreSQL unapplied patches list at:
http://candle.pha.pa.us/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
Gavin Sherry wrote:
> On Wed, 14 Aug 2002, Tom
Scott Shattuck <[EMAIL PROTECTED]> writes:
> Allow DBA/Database Owner to log in even when max_connections has
> been reached so they can determine which queries are hung via
> pg_stat_activity etc. and perform any other needed work to restore
> stability.
Allowing the database owner to login seem
I'm running Red Hat 7.3 at home. For the fun of it, I put:
#define NO_MKTIME_BEFORE_1970
into /src/include/port/linux.h and then did:
make clean
make all
make install
initdb
make installcheck
But I'm still getting the < 1970 regression test failures. What else do
I need to do?
Joe
---
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > Socket permissions - only install user can access db by default
> > unix_socket_permissions in postgresql.conf
>
> This is dead.
Removed, still on TODO.
> > glibc and mktime() - fix?
>
> Leave it be. If someone really
Tom Lane wrote:
> > I'm concerned, but in the few moments I've had to play with this, what
> > looked like the obvious fix didn't seem to work (I was hacking on glibc
> > itself though).
>
> Red Hat's internal opinion seems to be that "#define NO_MKTIME_BEFORE_1970"
> is a sufficient answer. I
Joe Conway wrote:
> > Fix bytea to not encode input string
> >
> > Not sure we can do these.
>
> As I said, it isn't clear to me how this can be fixed without a fe/be
> protocol change. But if someone can point me in the direction of a
> viable fix for 7.3, I'll dive in.
OK, item removed
> It's taken some real time and effort to get this list together, but many
> good people and many good companies have decided to stand up and show
> off that they use PostgreSQL for *serious* projects. For some, it's
> even Mission Critical.
Erm, Cisco uses PostgreSQL as an embedded database in
Neil Conway wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > remove interfaces/ssl if not improved
> >
> > I am ready to yank this.
>
> Agreed.
Done and item removed.
> > allow specification of configuration files in a different directory?
> >
> > Anyone working on this?
>
> N
OK, I removed this 7.3 open item and added a documentation item for the
release notes:
Mention foreign keys and SERIAL dependencies will not be in 7.2 loaded tables
---
Rod Taylor wrote:
> > Dependency - have pg_dump
Ross J. Reedstrom wrote:
> On Thu, Aug 15, 2002 at 11:05:07AM -0400, Bruce Momjian wrote:
> > I think we are going to see more company-funded developers working on
> > PostgreSQL. There are a handful now, but I can see lots more coming.
> > I am going to work on getting those funding companies mo
Robert Treat wrote:
> On Thu, 2002-08-15 at 17:13, Ross J. Reedstrom wrote:
> > On Thu, Aug 15, 2002 at 11:05:07AM -0400, Bruce Momjian wrote:
> > > I think we are going to see more company-funded developers working on
> > > PostgreSQL. There are a handful now, but I can see lots more coming.
> >
Hi everyone,
It's taken some real time and effort to get this list together, but many
good people and many good companies have decided to stand up and show
off that they use PostgreSQL for *serious* projects. For some, it's
even Mission Critical.
To compliment this, PostgreSQL Inc. is now offer
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > If we don't suffix global users with '@', a global user named 'dave'
> > could not attach to a database called 'db1' as himself if a user called
> > 'dave@db1' existed.
>
> No, it's the other way around (assuming you check user befor
Hello, I'm playing with creating an auto vacuum daemon, but it is my first
time inside the pg source code and I'm a bit lost.
I have gotten as far as having a vacuum daemon created on postmaster startup.
It's just a fork from the postmaster, cribbed mostly from the stat collector
code.
Insi
Hi,
I notice that the new default for the contrib Makefiles is to build
libfti.so, etc. instead of the old fti.so. Won't this cause dump restore
problems for everyone already using the contrib? Anyone mind if I change it
to use MODULES instead of MODULE_big for backwards compatibility?
Chris
Dang it...meant to mention that the other day when I was working on
those python patches. I had to place tick marks (single quote) around
the number and it was converted correctly.
gcope=# insert into a values ( 99 ) ;
ERROR: column "a" is of type 'bigint' but expression is of type 'dou
I was just testing my product running on a 7.3 snapshot from a few days
ago. And I ran into the following change in behavior that I consider a
bug. You can no long insert large values into a bigint column without a
cast. Small values (in the int range work fine though).
On 7.3 I get:
files
Bruce Momjian <[EMAIL PROTECTED]> writes:
> If we don't suffix global users with '@', a global user named 'dave'
> could not attach to a database called 'db1' as himself if a user called
> 'dave@db1' existed.
No, it's the other way around (assuming you check user before user@db):
the existence of
Ross - maybe we could work on a little function for tsearch - parse_query()
or something like that. It could return true or false depending on whether
it would cause tsearch to error or not...
Chris
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> I have seen some negative reactions to the feature. I am willing to ask
> for a vote, if that is what people want. If not, I will apply the patch
> in the next day or two.
Please apply.
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postm
Jan Wieck wrote:
> Bruce Momjian wrote:
> >
> > Allow PL/PgSQL functions to return sets
> >
> > Is anyone working on this? We will get beaten up if we don't have this
> > for 7.3 and it is available in other languages.
>
> That's true. I think I have to do this one. I'm busy for the ne
Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > I don't see what the problem is of dumping out the entire content of
> > pg_shadow into a flat file. First you look for a non-@ user, then you
> > look for an @ user that matches the database.
>
> While I'd prefer that approach m
On Thu, 2002-08-15 at 17:13, Ross J. Reedstrom wrote:
> On Thu, Aug 15, 2002 at 11:05:07AM -0400, Bruce Momjian wrote:
> > I think we are going to see more company-funded developers working on
> > PostgreSQL. There are a handful now, but I can see lots more coming.
> > I am going to work on getti
[EMAIL PROTECTED] (Vince Vielhaber) wrote
> Here we go again. I thought you just said that the @ wouldn't be
> something a user would have to do. I understood that to be any user.
> It's back to ugly again.
>
> Vince.
If it means anything to you, I agree that it should be a configure/compile
> Rod Taylor writes:
>
> > Anyone mind if we bump the DTD version to Docbook 4.2?
>
> Not sure if we should do this now. We're approaching the time where
> people should be writing documentation, not having to refiddle their
> carefully crafted DocBook installations. We're not going to realize
On Thu, Aug 15, 2002 at 11:05:07AM -0400, Bruce Momjian wrote:
> I think we are going to see more company-funded developers working on
> PostgreSQL. There are a handful now, but I can see lots more coming.
> I am going to work on getting those funding companies more visibility.
> We originally w
On Thu, Aug 15, 2002 at 11:59:20AM +0300, Oleg Bartunov wrote:
> tsearch has compiled-in stop-list, it's currently just not flexible
> as OpenFTS does. We plan to move most functionality to tsearch but
> currently have no time. Feel free to join us to speedup tsearch
> development.
Oleg -
I thin
Neil Conway <[EMAIL PROTECTED]> writes:
> Greg Copeland <[EMAIL PROTECTED]> writes:
>> I see. So the intension of the core developers is to have one and only
>> one replication solution?
> Not being a core developer, I can't comment on their intentions.
Well, I am, but I'm only speaking for mys
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> Switching the default is definitely fine with me, but I'd lean towards
>> ripping it out entirely, given that the backend-supplied chunks of stuff
>> are not going to have extra quotes. We always tell people "always quote
>> or ne
On Thu, 15 Aug 2002, Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > I don't see what the problem is of dumping out the entire content of
> > pg_shadow into a flat file. First you look for a non-@ user, then you
> > look for an @ user that matches the database.
>
> While I'd p
> --=-QQHYShMlxI2BY71i6NiO
> Content-Type: text/plain
> Content-Transfer-Encoding: quoted-printable
>
> > As I said -- I don't really see the need for a bunch of replication
> > implementations, and therefore I don't see the need for a generic API
> > to make the whole mess (slightly) more manage
A couple of admin nice-to-have's based on the last few weeks of 24x7
operation are:
Allow DBA/Database Owner to log in even when max_connections has been
reached so they can determine which queries are hung via
pg_stat_activity etc. and perform any other needed work to restore
stability.
Log off
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> I don't see what the problem is of dumping out the entire content of
> pg_shadow into a flat file. First you look for a non-@ user, then you
> look for an @ user that matches the database.
While I'd prefer that approach myself, the way Bruce is prop
On Thu, 2002-08-15 at 20:30, Peter Eisentraut wrote:
> Oliver Elphick writes:
>
> > I've implemented large file support for pg_dump, in what I hope is a
> > portable fashion. Please review the attached patch.
>
> Hmm, not quite right, but since you've indicated that you're not familiar
> with A
unsubscribe
> > Yes, after updating docs to the newer DTD I intend to make them XML
> > compliant to ensure they work with v5 of docbook in the future.
>
> Ah, an XML vs. SGML debate. I look forward to it.
This one is pretty simple. It's been announced that the docbook group
isn't looking to continue wit
Rod Taylor writes:
> Anyone mind if we bump the DTD version to Docbook 4.2?
Not sure if we should do this now. We're approaching the time where
people should be writing documentation, not having to refiddle their
carefully crafted DocBook installations. We're not going to realize any
immediate
Bruce Momjian writes:
> OK, I have another idea. What if we make global users end with an @, so
> dave@ is a global user. We can easily check for that in the postmaster
> and not append the dbname. I know it makes @ a special character, but
> considering the problem of namespace collision, it
Bruce Momjian writes:
> Socket permissions - only install user can access db by default
> unix_socket_permissions in postgresql.conf
This is dead.
> glibc and mktime() - fix?
Leave it be. If someone really needs time information from before 1970
(and who does?) he wo
Oliver Elphick writes:
> I've implemented large file support for pg_dump, in what I hope is a
> portable fashion. Please review the attached patch.
Hmm, not quite right, but since you've indicated that you're not familiar
with Autoconf I can take it from here.
--
Peter Eisentraut [EMAIL PRO
Tom Lane writes:
> Ah. But where exactly will you substitute true for 't'? I don't think
> pg_dump necessarily knows enough to apply that transformation.
Sure, it does it already for other types. Look for BITOID in pg_dump.c.
> Switching the default is definitely fine with me, but I'd lean t
all gone ...
On Thu, 15 Aug 2002, Vince Vielhaber wrote:
>
> Who the hell are these people and why can't they configure their
> own MTA?
>
> Vince.
> --
> ==
> Vince Vielhaber -- KA8CSHemail: [EMAIL PROTECTED]http:/
On Thu, 2002-08-15 at 13:18, Neil Conway wrote:
> That said, I _personally_ don't see the need for more than one or two
> replication implementations. You might need more than one if you
> wanted to do both lazy and eager replication, for example. But you
> certainly don't need 5 or 6 or however m
On Thu, 15 Aug 2002, Tom Lane wrote:
> Vince Vielhaber <[EMAIL PROTECTED]> writes:
> > But it doesn't need to affect anyone, even if it's enabled. Isn't
> > the lack of an @ just as good as an @ at the end of the username?
>
> No, because there isn't any @ in the incoming connection request in t
Vince Vielhaber <[EMAIL PROTECTED]> writes:
> Who the hell are these people and why can't they configure their
> own MTA?
>> Hi. This is the qmail-send program at ic.kharkov.ua.
>> I'm afraid I wasn't able to deliver your message to the following addresses.
>> This is a permanent error; I've give
Greg Copeland <[EMAIL PROTECTED]> writes:
> > As I said -- I don't really see the need for a bunch of replication
> > implementations, and therefore I don't see the need for a generic API
> > to make the whole mess (slightly) more manageable.
>
> I see. So the intension of the core developers is
> But how many people would even use it? I can't see adding the bloat
> unnecessarily and risking it accidently being turned on. Am I wrong
> and really alot of people actually want/need this?
At an absolute minimum there are two. Myself and Marc.
That said, this is a semi-required step to o
> As I said -- I don't really see the need for a bunch of replication
> implementations, and therefore I don't see the need for a generic API
> to make the whole mess (slightly) more manageable.
I see. So the intension of the core developers is to have one and only
one replication solution?
Gre
Greg Copeland <[EMAIL PROTECTED]> writes:
> In what way would providing a generic interface to *monitor* be a
> "waste of time"?
As I said -- I don't really see the need for a bunch of replication
implementations, and therefore I don't see the need for a generic API
to make the whole mess (slight
Of course, any funding information would be shared by the core group so
they are involved, but not shared to the general list until the company
wishes.
---
Andrew Sullivan wrote:
> I think I spelled -advocacy correctly thi
I am willing to talk to anyone about this. There is a reason my phone
number is in my signature (note new phone number; I just moved.)
Also, I am willing to make trips to companies to talk about PostgreSQL.
I can't make 100's of trips a year, but I try to do at least on a month.
I just did one
On Thu, 2002-08-15 at 09:53, Neil Conway wrote:
> That's exactly what I was going to say -- I'd prefer that any
> interested parties concentrate on producing a *really good*
> replication implementation, which might eventually be integrated into
> PostgreSQL itself.
>
> Producing a "generic API"
Yep, I just sent email to Marc to remove them.
---
Vince Vielhaber wrote:
>
> Who the hell are these people and why can't they configure their
> own MTA?
>
> Vince.
> --
>
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > + /* We append database name if db_user_namespace true. */
> > + #define SM_DATABASE_USER (SM_DATABASE+SM_USER)
>
> Is this calculation correct? I'd think you'd need at least one more
> character to allow for the "@". And I'm not s
I think I spelled -advocacy correctly this time.
On Thu, Aug 15, 2002 at 05:34:13PM +0200, Hans-J?rgen Sch?nig wrote:
> I think it would be a huge benefit for the community to have some more
> company-funding. This would lead to the implementation of some features
> people need urgently (replic
Andrew Sullivan <[EMAIL PROTECTED]> writes:
> On Wed, Aug 14, 2002 at 10:15:32PM -0500, Greg Copeland wrote:
> > Reading about the pgmonitor thread and mention of gborg made me wonder
> > about replication and ready ability to uniformly monitor it. Just as
> > pg_stat* tables exist to allow for s
Vince Vielhaber <[EMAIL PROTECTED]> writes:
> But it doesn't need to affect anyone, even if it's enabled. Isn't
> the lack of an @ just as good as an @ at the end of the username?
No, because there isn't any @ in the incoming connection request in the
normal-user case: just a user name and a dat
On Thu, 15 Aug 2002, Tom Lane wrote:
> Vince Vielhaber <[EMAIL PROTECTED]> writes:
> > Going from postgres to postgres@ ??? I don't care how simple the patch
> > is, I'd rather it was configurable to keep it out completely. That's
> > not just ugly, that's coyote ugly!
>
> Yeah, but it doesn't
On Thu, 2002-08-15 at 09:47, Andrew Sullivan wrote:
> On Wed, Aug 14, 2002 at 10:15:32PM -0500, Greg Copeland wrote:
> > That way, no matter what replication method/tool is being used, as long
> > as it conforms to the defined replication interfaces, generic monitoring
> > tools can be used to kee
Vince Vielhaber <[EMAIL PROTECTED]> writes:
> Going from postgres to postgres@ ??? I don't care how simple the patch
> is, I'd rather it was configurable to keep it out completely. That's
> not just ugly, that's coyote ugly!
Yeah, but it doesn't affect you unless you turn on the GUC parameter.
On Thursday 15 August 2002 11:54 am, Bruce Momjian wrote:
> OK, no one complained/commented on my idea of having global users have a
> trailing '@', so here is a patch that implements that. It has the
> advantages of:
As it's substantially the same as user@template1, I am of course OK with it.
On Thu, 15 Aug 2002, Tom Lane wrote:
> Other than getting the array sizes right, it does look like a nice
> patch; very small, which is what I'd hoped for. The notion of having to
> say "postgres@" still seems kinda ugly, but given the simplicity of the
> patch I'm willing to live with that.
Go
Bruce Momjian <[EMAIL PROTECTED]> writes:
> + /* We append database name if db_user_namespace true. */
> + #define SM_DATABASE_USER (SM_DATABASE+SM_USER)
Is this calculation correct? I'd think you'd need at least one more
character to allow for the "@". And I'm not sure about whether trailing
n
Who the hell are these people and why can't they configure their
own MTA?
Vince.
--
==
Vince Vielhaber -- KA8CSHemail: [EMAIL PROTECTED]http://www.pop4.net
56K Nationwide Dialup from $16.00/mo at Pop4 Netwo
On Thu, 15 Aug 2002, Bruce Momjian wrote:
> Vince Vielhaber wrote:
> > On Thu, 15 Aug 2002, Bruce Momjian wrote:
> >
> > > Vince Vielhaber wrote:
> > > > On Thu, 15 Aug 2002, Bruce Momjian wrote:
> > > >
> > > > >
> > > > > OK, no one complained/commented on my idea of having global users have a
Vince Vielhaber wrote:
> On Thu, 15 Aug 2002, Bruce Momjian wrote:
>
> > Vince Vielhaber wrote:
> > > On Thu, 15 Aug 2002, Bruce Momjian wrote:
> > >
> > > >
> > > > OK, no one complained/commented on my idea of having global users have a
> > > > trailing '@', so here is a patch that implements t
On Thu, 15 Aug 2002, Bruce Momjian wrote:
> Vince Vielhaber wrote:
> > On Thu, 15 Aug 2002, Bruce Momjian wrote:
> >
> > >
> > > OK, no one complained/commented on my idea of having global users have a
> > > trailing '@', so here is a patch that implements that. It has the
> > > advantages of:
>
On Thu, 15 Aug 2002, Bruce Momjian wrote:
>
> Vince, you were in the CC, and it went to hackers:
Oh, I'm not saying I didn't get it, I'm saying I didn't see it in
the message. It looked as if you were only replying to Tom so after
reading the jist of it I moved on. When you included it a littl
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > coming from 7.2 is going to cause problems in 7.3, i.e. do we make
> > assumptions that dependency info is there and in cases it isn't, are
> > there surprises for users, where things worked fine in 7.2. I want to
> > know if there a
Bruce Momjian <[EMAIL PROTECTED]> writes:
> coming from 7.2 is going to cause problems in 7.3, i.e. do we make
> assumptions that dependency info is there and in cases it isn't, are
> there surprises for users, where things worked fine in 7.2. I want to
> know if there are cases where we assumed
Vince Vielhaber wrote:
> On Thu, 15 Aug 2002, Bruce Momjian wrote:
>
> >
> > OK, no one complained/commented on my idea of having global users have a
> > trailing '@', so here is a patch that implements that. It has the
> > advantages of:
>
> Probably because not everyone saw it. I know I didn
Vince, you were in the CC, and it went to hackers:
Message 772/835 Bruce Momjian
Aug 14, 2002 08:30:47 pm -0400
Subject: Re: [HACKERS] Open 7.3 items
To: Tom Lane <[EMAIL PROTECTED]>
Date:
On Thu, 15 Aug 2002, Bruce Momjian wrote:
>
> OK, no one complained/commented on my idea of having global users have a
> trailing '@', so here is a patch that implements that. It has the
> advantages of:
Probably because not everyone saw it. I know I didn't. This entire
issue is growing more
Actually, my _big_ question is whether the lack of dependency info
coming from 7.2 is going to cause problems in 7.3, i.e. do we make
assumptions that dependency info is there and in cases it isn't, are
there surprises for users, where things worked fine in 7.2. I want to
know if there are cases
OK, no one complained/commented on my idea of having global users have a
trailing '@', so here is a patch that implements that. It has the
advantages of:
no special install user (create global user before enabling feature)
no /data/PG_INSTALLER file
allows multiple globa
I'm planning on trying out a version
of the check done for foreign keys that does
a query on the fktable with a NOT EXISTS
subselect rather than the current run the
trigger for each row (thus doing one query
per row of the table). I want to see if this
tends to be faster than what we're d
I will add something about the BSD license to the advocacy web page I am
trying to put together. My list is:
P O S T G R E S Q L
A D V O C A C Y
Current at ftp://candle.pha.pa.us/pub/postgresql/advocacy.
Quotations
Company users
B
I think it would be a huge benefit for the community to have some more
company-funding. This would lead to the implementation of some features
people need urgently (replication in the core and so forth). On the
other hand a better product makes even more developers work for
PostgreSQL. We were
I think we are going to see more company-funded developers working on
PostgreSQL. There are a handful now, but I can see lots more coming.
I am going to work on getting those funding companies more visibility.
We originally were concerned that such involvement may harm the
development process, b
On Wed, Aug 14, 2002 at 10:15:32PM -0500, Greg Copeland wrote:
> Reading about the pgmonitor thread and mention of gborg made me wonder
> about replication and ready ability to uniformly monitor it. Just as
> pg_stat* tables exist to allow for statistic gathering and monitoring in
> a uniform fa
On Thursday 15 August 2002 12:28 am, Tom Lane wrote:
> I think that's likely to be a hard sell. The most we are likely to get
> is to ask people to use the 7.3 pg_dump to dump their 7.2 server when
> they are about to upgrade to 7.3 --- even that much is a difficult trick
> for RPM users.
It's m
On Sun, Aug 11, 2002 at 11:12:57AM -0400, Tom Lane wrote:
> > Not solved yet. And it's just a matter of time until we run into it with
> > the main parser grammar file as well.
>
> Yeah, I've been worrying about that too. Any idea how close we are to
> trouble in the main grammar?
No idea. The
Well, that's a different issue. ;)
I initially wanted to get feedback to see if anyone else thought the
concept might hold some merit.
I take it from your answer you think it might...but are scratching your
head wondering exactly what it entails...
Greg
On Wed, 2002-08-14 at 22:47, Tom Lane
Yes, you can optionally specify the symbol to find in the *.so file as
part of the CREATE FUNCTION command.
---
Tom Lane wrote:
> "Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> > I guess my question would be that c
Mike Mascari <[EMAIL PROTECTED]> writes:
> I don't even know if "." is allowed in the schema names,
It isn't, and we couldn't invent such a scheme without seriously
diverging from SQL compliance: the next naming level up from schemas is
reserved for catalogs (think databases). I don't know that
On Thu, Aug 15, 2002 at 12:09:00AM -0400, Neil Conway wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
...
> > integrate or remove new libpqxx
> > integrate or add to gborg Pg:DBD
> >
> > Seems like gborg is the place for these.
>
> Yes, but I'd also like to see libpq++, perl5, and po
On Thu, 2002-08-15 at 11:41, Oliver Elphick wrote:
> I've implemented large file support for pg_dump, in what I hope is a
> portable fashion. Please review the attached patch.
> Index: src/bin/pg_dump/Makefile
> ===
> RCS file: /pro
I've implemented large file support for pg_dump, in what I hope is a
portable fashion. Please review the attached patch.
This needs an additional option from autoconf, because pg_dump prints a
hex offset which needs to be either %Lx or %llx, but there is no hex
equivalent to INT64_FORMAT. To ge
Christopher Kings-Lynne wrote:
[ ... ]
> What about this.
>
> 1. Implement pg_get_foreignkey_def() or whatever
> 2. Adjust pg_dump to dump foreign keys using an ALTER statement
> 3. Back port the above to rel 7_2_2
> 4. Release a 7.2.2 version and ask that people upgrade to that version and
> d
> tsearch has compiled-in stop-list, it's currently just not flexible
> as OpenFTS does. We plan to move most functionality to tsearch but
> currently have no time. Feel free to join us to speedup tsearch
> development.
Unfortunately I'm just as time-deprived :(
Chris
-
tsearch has compiled-in stop-list, it's currently just not flexible
as OpenFTS does. We plan to move most functionality to tsearch but
currently have no time. Feel free to join us to speedup tsearch
development.
Oleg
On Thu, 15 Aug 2002, Christopher Kings-Lynne wrote:
> Actually, lookin
Joe Conway wrote:
>
> Hannu Krosing wrote:
> > What about functions
> >
> > 1. split(text,text,int) returns text
> >
> > 2. split(text,text) returns text[]
> >
> > and why not
> >
> > 3. split(text,text,text) returns text
> >
> > which returns text from $1 delimited by $2 and $3
>
> Given the ti
100 matches
Mail list logo
