> I'm wondering if maybe the Right Thing(TM) might be for all
> connections to return (optionally?) the version number, but that seems
> like a giant project with many backward-compatibility snags attached.
I think it would be for psql to check the connection version and then load a
shared library
Kind people,
I've been digging through the CVS code and trying to figure out the
best approach to making one psql that "does the right thing" for
different versions of the back-end. This has come up in a real
situation already, where the dev box is 7.3.3 and the production box
is (Yikes!) 7.2.1.
Because 7.4 had more parallel CVS branch changes than previous releases,
I decided to pull cvs logs based only on the CVS HEAD, so I didn't get
commits to branches.
I used this command:
cvs log -d'>2002-11-04 00:00:00 GMT' -rHEAD .
I then ran it through tools/pgcvslog and started working
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> Somehow, when we moved it to gborg way back, the 'cvs remove' wasn't done
> on the mail repository ... there ... cvs remove'd now, so its still part
> of v7.3.x, but no longer part of v7.4 ...
According to the CVS logs, there were several patches ap
> > I actually had this while I was developing the feature.
>
> And what platform are *you* on? It seems a really hard-to-believe
> bug...
This will actually be a must-fix for 7.4, as pg_dump uses it now to dump
triggers...
Chris
---(end of broadcast)---
On Fri, 1 Aug 2003, Bruce Momjian wrote:
>
> OK, any idea why I see it in my CVS? It was recently completely checked
> out.
Somehow, when we moved it to gborg way back, the 'cvs remove' wasn't done
on the mail repository ... there ... cvs remove'd now, so its still part
of v7.3.x, but no longer
I haven't removed teh stuff out of configure.in, since there is still the
plpython interface ...
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
> > Hmmm...looks like on my system english_stem.d is created in the tsearch2
> > dir, NOT in the snowball subdir.
>
> I see no english_stem.d at all. I speculate that this is a temp file
> created during the gcc run, and that your gcc driver is brain-damaged
> about compiling files that aren't in
>> I still see the python interface in src/interfaces. Marc, I thought you
>> moved that to gborg?
I still see it too ... and so does cvsweb:
http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/interfaces/python/
regards, tom lane
---(end
actually, the whole python interface was moved over to
http://www.pygresql.org ...
On Thu, 31 Jul 2003, Bruce Momjian wrote:
> I still see the python interface in src/interfaces. Marc, I thought you
> moved that to gborg?
>
> --
> Bruce Momjian| http://candle.pha.pa
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> gcc -pipe -O -g -Wall -Wmissing-prototypes -Wmissing-declarations -fpic -DPI
>
> -I. -I. -I./snowball -I./ispell -I./wordparser -I../../src/include -c -o
> snowball/english_stem.o snowball/english_stem.c -MMD
> cp: snowball/english_stem.d:
OK, any idea why I see it in my CVS? It was recently completely checked
out.
---
Marc G. Fournier wrote:
>
> actually, the whole python interface was moved over to
> http://www.pygresql.org ...
>
>
>
> On Thu, 31 Jul 2
> >
gcc -pipe -O -g -Wall -Wmissing-prototypes -Wmissing-declarations -fpic -DPI
> >
-I. -I. -I./snowball -I./ispell -I./wordparser -I../../src/include -c -o
> > snowball/english_stem.o snowball/english_stem.c -MMD
> > cp: snowball/english_stem.d: No such file or directory
> > gmake[1]: *** [snow
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> I didn't see any probs with the ones you fixed, but I see this:
> prs_dcfg.c: In function `parse_cfgdict':
> prs_dcfg.c:65: warning: int format, different type arg (arg 2)
> prs_dcfg.c:78: warning: int format, different type arg (arg 2)
> prs
I still see the python interface in src/interfaces. Marc, I thought you
moved that to gborg?
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
>> This leaves some issues still to be
>> resolved ... like what to do when dumping a pre-7.3 database ... but I
>> think it's the core of a maintainable solution.
> Problem is you'd need to sort tables by the youngest column in the table,
> wh
> What I'd like to see it do is grab the dependency data in pg_depend and
> do a topological sort using that.
At the end though, we'd need to dump stuff not caught be the topsort, for
cases where pg_depend has been messed with.
> This leaves some issues still to be
> resolved ... like what to do
> Fixed, I think. Give it another try.
I didn't see any probs with the ones you fixed, but I see this:
gmake[1]: Entering directory `/home/chriskl/pgsql-temp/contrib/tsearch2'
sed 's,DATA_PATH,/home/chriskl/local/share/postgresql,g' < tsearch.sql._in >
tsearch2.sql.in
sed 's,MODULE_PATHNAME,$lib
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> Can someone tell me know what has to be done to pg_dump to make it dump
> things in the right order? Where should I start. The most important thing
> is getting types dumped before tables that use the type.
What I'd like to see it do is gra
Actually, I never made the change until now. I thought I had already
did it. Sorry.
---
pgman wrote:
>
> Change made.
>
> ---
>
> Tom Lane wrote:
>
Hi,
Can someone tell me know what has to be done to pg_dump to make it dump
things in the right order? Where should I start. The most important thing
is getting types dumped before tables that use the type.
Chris
---(end of broadcast)---
TIP 2:
> > I actually had this while I was developing the feature.
>
> And what platform are *you* on? It seems a really hard-to-believe
> bug...
FreeBSD/i386 I developed it on.
Chris
---(end of broadcast)---
TIP 6: Have you searched our list archives?
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> I just tried compiling all contribs on freebsd/alpha, and I saw these
> issues:
Fixed, I think. Give it another try.
regards, tom lane
---(end of broadcast)---
TIP 6:
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
>> Bizarre. It looks fine here. What platform are you on? Anyone else
>> see this?
> I actually had this while I was developing the feature.
And what platform are *you* on? It seems a really hard-to-believe
bug...
> > Triggers:
> > my_little^trigger BEFORE UPDATE ON test FOR EACH STATEMENT EXECUTE
PROCEDURE foofun()
>
> Bizarre. It looks fine here. What platform are you on? Anyone else
> see this?
I actually had this while I was developing the feature. I had thought I had
fixed it. It's basically t
I said:
> Alvaro Herrera Munoz <[EMAIL PROTECTED]> writes:
>> $ createlang -d alvherre plpgsql
>> createlang: language installation failed: ERROR: c: permission denied
>> What's the "c" it's complaning about?
> The C procedural language, presumably. This message is not up to our new
> message st
I was starting to wonder if my message got there.
Tom had asked for a clear definition of "what is a
statement" hence the wide description.
If I wrote this up more formally where would I put
it so we could talk about it when the various issues
come up? Maybe a friend-of-the-court unapproved func
There seems to be some disagreement on whether the Oracle lib checks
should be in configure for a /contrib module, and I don't know how far
Hans is. I will say we are probably looking at 7/28 for beta.
I am afraid I won't make it until 7.4beta1.
The problem is that I have not managed to have mor
HI
I am running MFcobol on a linux machine which is
having Postgresql. can I access pgsql database thru
mfcobol.
If it is possible where can I get odbc drivers and
what is the procedure help me
chakravarthi
Send free SMS us
When a SELECT FOR UPDATE query is executed, are the row level locks on a
table acquired in any specific order such as to enhance deadlock
prevention? ( primary key, oid, etc. )
---(end of broadcast)---
TIP 8: explain analyze is your friend
The semantics of this conceptually is not too
bad. The implementation could be tricky.
For any given DML or sub-DML (select, eg) the scope
should be for that DML. The DML is the "parent"
of the function. The DML is the statement
context and the function is the function
context.
statement --
On Tue, 2003-07-29 at 13:16, Shridhar Daithankar wrote:
> On 29 Jul 2003 at 13:07, Andreas Jung wrote:
>
> > On Tue, 2003-07-29 at 13:02, Shridhar Daithankar wrote:
> > > On 29 Jul 2003 at 12:48, Andreas Jung wrote:
> > > > Our experience was that the complete table has been locked (Solaris)
> > >
On Tue, 2003-07-29 at 13:02, Shridhar Daithankar wrote:
> On 29 Jul 2003 at 12:48, Andreas Jung wrote:
>
> > On Tue, 2003-07-29 at 12:42, Shridhar Daithankar wrote:
> > > On 29 Jul 2003 at 12:33, Andreas Jung wrote:
> > > > we are running Postgres 7.3.3 successfully on our portal sites
> > > > und
Hello Bruce,
Thursday, July 24, 2003, 11:05:21 PM, you wrote:
BM> Marcus B?rger wrote:
>> >> BM> I don't see why you wouldn't just do BEGIN;COMMIT;RESET ALL; when you
>> >> BM> pass the connection to a new client.
>> >>
>> >>
>> >> Bruce you said RESET ALL is available since 7.2. I am currently
Hello Bruce,
Wednesday, July 23, 2003, 6:18:13 AM, you wrote:
BM> Marcus B?rger wrote:
>> >> However it may be very usefull to terminate any open transaction before
>> >> reusing a persisten connection. Typically this happens when the same script
>> >> runs again. But anyway using transactions to
There was an article about a LARGE storage network of linux boxes I saw recently. Absolutely stable. Wish I could tell you where it was, but I can't.
Lamar Owen wrote:
Good evening.
RPMs for PostgreSQL 7.3.4, built on three architectures, are in the midst of
uploading to ftp.postgresql.org, in
Hello Bruce,
Thursday, July 24, 2003, 11:57:39 PM, you wrote:
BM> Jan Wieck wrote:
>> Marcus B?rger wrote:
>> > ATM i have a patch doing the following:
>> > Connect:
>> > If PQprotocolVersion() is available and >= 3 PQparameterStatus() is available
>> > then i check the server version. Else i c
Alvaro Herrera Munoz <[EMAIL PROTECTED]> writes:
> $ createlang -d alvherre plpgsql
> createlang: language installation failed: ERROR: c: permission denied
> What's the "c" it's complaning about?
The C procedural language, presumably. This message is not up to our new
message standards I suppose
Hackers,
Two buglets:
The first one is in createlang, trying to create a language without
enough permission:
$ createlang -d alvherre plpgsql
createlang: language installation failed: ERROR: c: permission denied
What's the "c" it's complaning about?
The second one is in pg_get_triggerdef():
Why postgres should be using only for standard ways ?
I need to protect pg how its possible . Every single informacion which
user dont need to know he can not know . Each user is like enemy . :-)
I worry more about this cache , i dont know how to reset it.
Beca use i (in one transaction) make co
Bruce Momjian wrote:
That was my feeling. Also, I was concerned that non-native English
speakers might not have heard of 'terse', while max/min or off/full
would be more common.
Possibly plenty of "English" speakers, too ;-)
andrew
---(end of broadcast)---
Josh Berkus <[EMAIL PROTECTED]> writes:
> Putting on marketing hat:
> While branding is important, unlike other projects the shortened version of
> our name is still distinctive and unique ... "Postgres" is unlikely to be
> mistaken for anything else.
Also, we should continue to use it reasona
I thought so too, but I had to ask.
---
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > I see all submitted patches as applied, except from Gavin's WHERE
> > CURRENT OF patch, and I am asking for opinions on that one.
On Wed, Jul 30, 2003 at 04:18:39PM -0400, Lamar Owen wrote:
>
> What Andrew is saying is that on some IDE drives it doesn't matter
> what the OS tells the drive to do. According to the Linux hdparm
Right. In other words, you can't really trust IDE drives, until the
manufacturers start guarantee
On Wed, Jul 30, 2003 at 10:33:55PM -0400, Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom, you saw this suggestion, right?
>
> I didn't hear anyone else agreeing with it ...
Well, if this needs a vote, I'm for something like maximum/default/minimum
rather than the way it curre
Does anyone know anything about pkgconfig?
---
John Huttley wrote:
> On Thu, 2003-07-31 at 16:36, Bruce Momjian wrote:
> > I have no idea what that is.
>
> This is the home page. If you have modern distribution with develop
Alvaro Herrera Munoz wrote:
> On Wed, Jul 30, 2003 at 10:33:55PM -0400, Tom Lane wrote:
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > Tom, you saw this suggestion, right?
> >
> > I didn't hear anyone else agreeing with it ...
>
> Well, if this needs a vote, I'm for something like maximum/de
> Alvaro Herrera Munoz wrote:
>> Well, if this needs a vote, I'm for something like maximum/default/minimum
>> rather than the way it currently is. Saying "verbosity verbose" or
>> "verbosity terse" doesn't feel right, while "verbosity maximum" makes
>> sense, to me anyway.
"max" would work for t
Manfred,
> Can't this be done on postmaster startup? I think of two GUC
> variables where there is only one today: min_shared_buffers and
> max_shared_buffers. If allocation for the max_ values fails, the
> numbers are decreased in a loop of, say, 10 steps until allocation
> succeeds, or even fa
Tom Lane writes:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > Nonetheless, I think a pg_dump 7.3.2 dumping a 7.3.3 database should not
> > raise a version mismatch message at all.
>
> I'm unconvinced; at best, you are assuming zero bugs.
Yes. The version mismatch message wasn't created bec
Chris,
> I just seem to recall a discussion where we decided to 'standardise' on
> PostgreSQL...I'm not fussed tho.
Putting on marketing hat:
While branding is important, unlike other projects the shortened version of
our name is still distinctive and unique ... "Postgres" is unlikely to be
mi
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> On my 7.3 server:
> REVOKE ALL ON TABLE exercise_activities FROM PUBLIC;
> GRANT ALL ON TABLE exercise_activities TO chriskl;
> GRANT SELECT ON TABLE exercise_activities TO "au-diary";
> GRANT SELECT ON TABLE exercise_activities TO "au-php";
Manfred Koizar <[EMAIL PROTECTED]> writes:
> On Fri, 04 Jul 2003 15:29:37 -0400, Tom Lane <[EMAIL PROTECTED]>
> wrote:
>> The attached patch shows how initdb can dynamically determine reasonable
>> shared_buffers and max_connections settings that will work on the
>> current machine.
> Can't this b
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Nonetheless, I think a pg_dump 7.3.2 dumping a 7.3.3 database should not
> raise a version mismatch message at all.
I'm unconvinced; at best, you are assuming zero bugs. I think the
warning message is reasonable as it stands, and that what Chris ough
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> Peter, I'm a little confused about the difference between the libdir and
>> pkglibdir settings created by configure. What's supposed to go where?
> libdir is for build-time linkable libraries, anything that you might want
> to pas
Oleg Bartunov <[EMAIL PROTECTED]> writes:
> I'm confused with pg_dump -t '*', it doesn't works as expected
> from pg_dump --help:
> -t, --table=TABLEdump this table only (* for all)
The help is mistaken --- that is not a working feature. Leave out the
-t if you want all tables.
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > The issue I have is that every interface that relies on libpq is going
> > to have to code it itself. Is that OK?
>
> So? Most interfaces have to adhere to their own notions of transaction
> semantics and control API anyway. libpq
We wouldn't like to have it called Ingres too...
Spoken language is different from written, so docs should be precise.
PostgreSQL is a mark, and should be used as careful as it deserves.
Regards,
Andreas
Christopher Kings-Lynne wrote:
I just seem to recall a discussion where we decided to 'stand
On Fri, 04 Jul 2003 15:29:37 -0400, Tom Lane <[EMAIL PROTECTED]>
wrote:
>The attached patch shows how initdb can dynamically determine reasonable
>shared_buffers and max_connections settings that will work on the
>current machine.
Can't this be done on postmaster startup? I think of two GUC
varia
Bruce Momjian writes:
> If we change default_transaction_read_only to PGC_USERLIMIT, the
> administrator can turn it on and off, but an ordinary user can only turn
> it on, but not off.
> Would that help?
No, it would break the SQL standard.
--
Peter Eisentraut [EMAIL PROTECTED]
Hi there,
I'm confused with pg_dump -t '*', it doesn't works as expected
from pg_dump --help:
-t, --table=TABLEdump this table only (* for all)
I tried any combinations but never succeeded.
Regards,
Oleg
Tom Lane writes:
> Peter, I'm a little confused about the difference between the libdir and
> pkglibdir settings created by configure. What's supposed to go where?
libdir is for build-time linkable libraries, anything that you might want
to pass as -lxxx. So typical locations are /usr/lib, /usr
Sean Chittenden writes:
> At the very least, it's an easier way of guaranteeing a READ ONLY
> database. Securing a database with GRANT/REVOKE can be tedious and
> error prone.
A database is already secure from a new user by default: He cannot read or
write or create anything except temporary tab
Christopher Kings-Lynne writes:
> I get this in my logs from our backups. I ahve explicitly put -i in
> pg_dumpall. How about we totally suppress this message if -i is supplied,
> because obviously the person knows perfectly well it's proceeding despite
> version mismatch?
I think if we did tha
Bruce Momjian writes:
> I see all submitted patches as applied, except from Gavin's WHERE
> CURRENT OF patch, and I am asking for opinions on that one.
I think it's too late for that one.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)-
65 matches
Mail list logo
