Hi Tom,
How about we include this and have configure somehow ensure the Solaris
users get it automatically?
There are a *bunch* of Solaris users out there.
:-)
Regards and best wishes,
Justin Clift
Mark kirkwood wrote:
>
> On Wed, 2002-04-03 at 04:02, Tom Lane wrote:
> >
> > Hmm. Where e
> -Original Message-
> From: Christopher Kings-Lynne [mailto:[EMAIL PROTECTED]]
> Sent: 03 April 2002 02:50
> To: Hackers
> Cc: Tom Lane; [EMAIL PROTECTED]
> Subject: SHOW ALL as a query result
>
>
> Hi All,
>
> Now that Tom's modified the EXPLAIN output to appear as a
> query resul
>>>Tom Lane said:
> Daniel Kalchev <[EMAIL PROTECTED]> writes:
> > So in essence this means that my best bet is to again dump/reload the
> > database...
>
> Either that or fix your queries to cast the literals explicitly.
Sorry for the incomplete reply:
this does not work:
customer=# sel
>>>Tom Lane said:
> Daniel Kalchev <[EMAIL PROTECTED]> writes:
> > So in essence this means that my best bet is to again dump/reload the
> > database...
>
> Either that or fix your queries to cast the literals explicitly.
There is more to it:
customer=# select max(oid) from croute;
m
You can stop the postmaster and start the postgres binary with the -O
flag and delete the pg_temp tables. We don't have a cleanup for these
failed backends but we should. Normally they are cleaned up.
---
Daniel Kalchev w
I found out, that there are some probably temporary relations in one of my
databases, with names (that show in vacuum verbose output) like
pg_temp.12720.0.
Are these the result of CREATE TEMP TABLE or simmilar and if so, can such
relations be safely dropped? Perhaps a good idea to add some vac
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> The determination of locale is now done as follows:
> initdb --lc-collate, initdb --locale, LC_ALL, LC_COLLATE, LANG
> initdb --no-locale is the same as initdb --locale=C, for convenience.
I'm confused; what is the default behavior if you don't give
The determination of locale is now done as follows:
collate/ctype:
initdb --lc-collate, initdb --locale, LC_ALL, LC_COLLATE, LANG
messages/monetary/numeric/time:
Have GUC variables lc_messages, etc. The default is "", which means to
inherit from the environment (or whatever setlocale() does w
What's with this?
current pwd = /home/chriskl
usa=# \i ddlpack/kl_setnotnull.sql <-- tab completes properly
DROP
CREATE
usa=# \i ~/ddlpack/kl_setnotnull.sql <-- tab completes properly
~/ddlpack/kl_setnotnull.sql: No such file or directory
usa=#
Chris
---(end of bro
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> I was forced to put SYMMETRIC and ASYMMETRIC as reserved words - anything
> else seemed to give shift/reduce errors. Is there anything I can do about
> that?
First thought is "don't try to be cute": forget the opt_asymmetry
clause, and inst
On Tue, 02 Apr 2002 23:39:35 -0500
"Tom Lane" <[EMAIL PROTECTED]> wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > Well, for one thing, we might want to change the name to the correct
> > spelling "cacheable".
>
> Is that correct?
Apparently, other people are confused as well:
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Well, for one thing, we might want to change the name to the correct
> spelling "cacheable".
Is that correct?
I looked in the Oxford English Dictionary, the Random House Dictionary,
and a couple other dictionaries of less substantial heft, and could
*sigh*
I actually attached the diff this time...
Chris
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Christopher
> Kings-Lynne
> Sent: Wednesday, 3 April 2002 12:26 PM
> To: Hackers
> Subject: [HACKERS] BETWEEN SYMMETRIC/ASYMMETRIC
>
>
> Hi All,
Hi All,
As part of my ongoing quest to understand grammar files, I've been trying to
implement BETWEEN SYMMETRIC/ASYMMETRIC.
I've attached my current work. Can someone please look and tell me if I'm
on the right track? With this patch, I get parse errors after BETWEEN if I
go:
SELECT 2 BETWEE
Gavin Sherry <[EMAIL PROTECTED]> writes:
> On Wed, 3 Apr 2002, Christopher Kings-Lynne wrote:
>> Would it be an idea to have pg_dump append an ANALYZE; command to the end of
>> its dumps to assist newbies / inexperienced admins?
> I do not think this is desired behaviour.
I agree with Gavin here
Christopher Kings-Lynne wrote:
> Hi All,
>
> Now that Tom's modified the EXPLAIN output to appear as a query
> result, maybe SHOW and SHOW ALL should also be modified in that way.
> The current NOTICE: business is a bit messy, and it sure would
> assist projects just as pgAccess, phpPgAdmin
Christopher Kings-Lynne writes:
> Now that Tom's modified the EXPLAIN output to appear as a query result,
> maybe SHOW and SHOW ALL should also be modified in that way. The current
> NOTICE: business is a bit messy, and it sure would assist projects just as
> pgAccess, phpPgAdmin and pgAdmin wit
On Wed, 3 Apr 2002, Christopher Kings-Lynne wrote:
> Hi,
>
> Would it be an idea to have pg_dump append an ANALYZE; command to the end of
> its dumps to assist newbies / inexperienced admins?
I do not think this is desired behaviour. Firstly, pg_dump is not just for
restoring data to the system
On Wed, 3 Apr 2002 09:40:13 +0800
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Would it be an idea to have pg_dump append an ANALYZE; command to the end of
> its dumps to assist newbies / inexperienced admins?
That strikes me as a good idea; a lot of the questions we get on
-ge
Hi All,
Now that Tom's modified the EXPLAIN output to appear as a query result,
maybe SHOW and SHOW ALL should also be modified in that way. The current
NOTICE: business is a bit messy, and it sure would assist projects just as
pgAccess, phpPgAdmin and pgAdmin with displaying configuration!
Als
On Tue, 2 Apr 2002, Peter Eisentraut wrote:
> Tom Lane writes:
>
> > Since I'm about to have to edit pg_proc.h to add a namespace column,
> > I thought this would be a good time to revise the current proiscachable
> > column into the three-way cachability distinction we've discussed
> > before.
Hi,
Would it be an idea to have pg_dump append an ANALYZE; command to the end of
its dumps to assist newbies / inexperienced admins?
Reason being is that I noticed that when I just restored a 50MB dump that
the pg_statistic table had no contents...
I think it'd be an idea...
Chris
--
Tom Lane writes:
> Since I'm about to have to edit pg_proc.h to add a namespace column,
> I thought this would be a good time to revise the current proiscachable
> column into the three-way cachability distinction we've discussed
> before. But I need some names for the values, and I'm not satisf
Since both the JDBC and ODBC specs have essentially the same symantics
for this, I would hope this is done in the backend instead of both
interfaces.
--Barry
Jessica Perry Hekman wrote:
> On Mon, 1 Apr 2002, Tom Lane wrote:
>
>
>>On the other hand, we do not have anything in the backend now
* Tom Lane ([EMAIL PROTECTED]) [020402 16:42]:
> Since I'm about to have to edit pg_proc.h to add a namespace column,
> I thought this would be a good time to revise the current proiscachable
> column into the three-way cachability distinction we've discussed
> before. But I need some names for t
Tom Lane wrote:
> BTW, because of MVCC semantics, case 2 covers more ground than you might
> think. We are interested in functions whose values cannot change during
> a single "scan", ie, while the intra-transaction command counter does
> not increment. So functions that do SELECTs are actually
My 2 cents.
Level 1. with (isCachableStatic)
Level 2. with (isCachableDynamic)
Level 3. default
In my mind (isCachable) sounds like level 1
On Tuesday 02 April 2002 03:40 pm, Tom Lane wrote:
> Since I'm about to have to edit pg_proc.h to add a namespace column,
> I thought this would be a good
Since I'm about to have to edit pg_proc.h to add a namespace column,
I thought this would be a good time to revise the current proiscachable
column into the three-way cachability distinction we've discussed
before. But I need some names for the values, and I'm not satisfied
with the ideas I've ha
Daniel Kalchev <[EMAIL PROTECTED]> writes:
> So in essence this means that my best bet is to again dump/reload the
> database...
Either that or fix your queries to cast the literals explicitly.
regards, tom lane
---(end of broadcast)-
>>>Tom Lane said:
> This is one of a whole raft of cases involving undesirable assignment
> of types to numeric constants; see past complaints about int4 being used
> where int2 or int8 was wanted, numeric vs float8 constants, etc etc.
> We're still looking for a promotion rule that does what
Daniel Kalchev <[EMAIL PROTECTED]> writes:
> It turned out to be an query containing "oid = somenumber" called from perl script.
>Is it possible that the default type conversion functions do not work as expected?
No, but you do have to cast an oversize value to oid explicitly to
prevent it from
An followup to my previous post.
It turned out to be an query containing "oid = somenumber" called from perl script. Is
it possible that the default type conversion functions do not work as expected?
Changing this to "oid = oid(somenumber)" worked as expected.
Daniel
Alex Lau <[EMAIL PROTECTED]> writes:
> CREATE TABLE mytesting ( dosnotmatter text );
> CREATE INDEX myunique ON mytesting oid;
> will this help to make sure the oid is unique?
No, but
CREATE UNIQUE INDEX myunique ON mytesting (oid);
would do the trick.
regards, tom lan
Has anyone seen this:
ERROR: dtoi4: integer out of range
on 7.1.3
What worries me, is that at startup time, the log shows:
DEBUG: database system was shut down at 2002-04-02 23:16:52 EEST
DEBUG: CheckPoint record at (82, 1928435208)
DEBUG: Redo record at (82, 1928435208); Undo record at (
Reinoud van Leeuwen wrote:
> Hi,
>
> We are implementing a database for maintaining our IP addresses. Looking
> in the current documentation, it seems that INET/CIDR types only support
> IPv4 addresses until now, although
> http://archives.postgresql.org/pgsql-patches/2001-09/msg00236.php
> se
On Tue, 2 Apr 2002, Bruce Momjian wrote:
> BEGIN WORK;
> query;
> SET statement_timeout = 4;
> query;
> SET statement_timeout = 0;
> query;
> COMMIT;
> SET statement_timeout = 0;
>
> Basically, it does the reset twice, once assuming the transaction
Jessica Perry Hekman wrote:
> On Tue, 2 Apr 2002, Bruce Momjian wrote:
>
> > BEGIN WORK;
> > query;
> > SET statement_timeout = 4;
> > query;
> > SET statement_timeout = 0;
> > query;
> > COMMIT;
> > SET statement_timeout = 0;
> >
> > Basically, it does the reset
Rod Taylor wrote:
> Out of curiousity, what happens if the remove server is unavailable?
>
I tried it against a bogus IP, and this is what I got:
test=# select dblink_tok(t1.dblink_p,0) as f1, dblink_tok(t1.dblink_p,1)
as f2 from (select dblink('hostaddr=123.45.67.8
dbname=template1','select
Is PostgreSQL unicode compliant/ready?
Does it store/export text in Unicode wide-character format, or single
character strings?
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail comman
Jessica Perry Hekman wrote:
> On Mon, 1 Apr 2002, Tom Lane wrote:
>
> > On the other hand, we do not have anything in the backend now that
> > applies to just one statement and then automatically resets afterwards;
> > and I'm not eager to add a parameter with that behavior just for JDBC's
> > co
Create a separate user and both of you use sudo to start the database.
If you're insistent on keeping yourself owner of the data then use sudo to
give permission to your project partner to start the database.
On Sunday 31 March 2002 05:49 am, Amit Khare wrote:
> Hi Peter,
> Thank you very much f
I was wondering if it is documented as to exactly how to do a minor
upgrade. I've not been able to find it in the past, and I end up doing
a full install, dump/reload. I'm running postgresql on nt/2000 using
cygwin. Thanks -Dean
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
CREATE TABLE mytesting ( dosnotmatter text );
CREATE INDEX myunique ON mytesting oid;
will this help to make sure the oid is unique? and is that right?
if in fact the oid roll over, and insertation fail. Will reinsert get
an new oid or the same oid retry.
Alex
---(en
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.
---
Gilles DAROLD wrote:
> Hi Justin,
>
> I have
Out of curiousity, what happens if the remove server is unavailable?
- Original Message -
From: "Joe Conway" <[EMAIL PROTECTED]>
To: "Darko Prenosil" <[EMAIL PROTECTED]>
Cc: "Hackers" <[EMAIL PROTECTED]>
Sent: Tuesday, April 02, 2002 12:58 PM
Subject: Re: [HACKERS] Dblink and ISDN
>
Generally, what is the duration between such an announcement and the
appearence of
the RPMs found on the Download PostgreSQL page?
Also, the http://www.us.postgresql.org/news.html has no mention of this
upgrade.
Thanks.
Richard
"Marc G. Fournier" wrote:
> Over this past weekend, the Postgre
Hi,
We are implementing a database for maintaining our IP addresses. Looking
in the current documentation, it seems that INET/CIDR types only support
IPv4 addresses until now, although
http://archives.postgresql.org/pgsql-patches/2001-09/msg00236.php
seems to suggest a patch for IPv6 has been
Original titles:
Patch to add real cancel to ODBC driver
Patch to add real can--cel to ODBC driver
Bruce, sorry to bother you, would you forward this onto the list?
I can't post for reasons I can't fathom.
-
Patch against 7,2 submitted for comment.
It's a little messy; I had some trouble
I'm working on getting libpq to function in a multi-threaded program on
Solaris and I was getting errors back from the library about
being unable to receive from the server. It turns out that on Solaris
you need to compile libpq with the -D_REENTRANT flags set so that
it defines errno to be a fun
Patch against 7,2 submitted for comment.
It's a little messy; I had some trouble trying to reconcile the code
style of libpq which I copied from, and odbc.
Suggestions on what parts look ugly, and or where to send this
(is there a separate ODBC place?) are welcome.
This seems to work just fine;
I have a postgresql DB that contains a lot of HTML code. As you know, HTML
contains numerous backslash( \ ) characters. When I use pg_dump to backup
the DB I get a "CopyReadAttribute: end of record marker corrupted" error.
Is there any way to circumvent this problem so that I can backup a DB
OK,
http://members.iinet.net.au/~klfamily/alternotnull.txt.gz
This is an identical patch to what I've submitted twice now and hasn't come
through...
This is a complete patch to implement changing the nullability of an
attribute. It passes all regressions tests. It includes its own quite
compr
This is a complete patch to implement changing the nullability of an
attribute. It passes all regressions tests. It includes its own quite
comprehensive regression test suite and documentation. It prevents you from
modifying system tables, non-table relations, system attributes, primary
keys an
Joe Conway wrote:
> Darko Prenosil wrote:
>
>> SAMPLE:
>>
>> create view myremotetable as
>> select dblink_tok(t1.dblink_p,0) as f1, dblink_tok(t1.dblink_p,1) as f2
>> from (select dblink('hostaddr=127.0.0.1 port=5432 dbname=template1
>> user=postgres password=postgres'
>>
OK. Here is a test posting to hackers and Ccing to Marc
Oleg
On Tue, 26 Mar 2002, Marc G. Fournier wrote:
>
> ah, then that's gotta be it ... can you do me a favor and email
> pgsql-hackers a simple test, so that I can get the email out of hte
> approved messages and show you what I'm se
Darko Prenosil wrote:
> SAMPLE:
>
> create view myremotetable as
> select dblink_tok(t1.dblink_p,0) as f1, dblink_tok(t1.dblink_p,1) as f2
> from (select dblink('hostaddr=127.0.0.1 port=5432 dbname=template1
> user=postgres password=postgres'
> ,'select proname, prosrc fro
On Tue, 2 Apr 2002, Tom Lane wrote:
> Vince Vielhaber <[EMAIL PROTECTED]> writes:
> > On Tue, 2 Apr 2002, Richard Emberson wrote:
> >> Generally, what is the duration between such an announcement and the
> >> appearence of
> >> the RPMs found on the Download PostgreSQL page?
> >>
> >> Also, the
Vince Vielhaber <[EMAIL PROTECTED]> writes:
> On Tue, 2 Apr 2002, Richard Emberson wrote:
>> Generally, what is the duration between such an announcement and the
>> appearence of
>> the RPMs found on the Download PostgreSQL page?
>>
>> Also, the http://www.us.postgresql.org/news.html has no ment
On Tue, 2 Apr 2002, Richard Emberson wrote:
> Generally, what is the duration between such an announcement and the
> appearence of
> the RPMs found on the Download PostgreSQL page?
>
> Also, the http://www.us.postgresql.org/news.html has no mention of this
It takes up to 24 hours for all of the
On Mon, 1 Apr 2002, Tom Lane wrote:
> On the other hand, we do not have anything in the backend now that
> applies to just one statement and then automatically resets afterwards;
> and I'm not eager to add a parameter with that behavior just for JDBC's
> convenience. It seems like it'd be a big
"Dean Hill" <[EMAIL PROTECTED]> writes:
> I was wondering if it is documented as to exactly how to do a minor
> upgrade. I've not been able to find it in the past, and I end up doing
> a full install, dump/reload. I'm running postgresql on nt/2000 using
> cygwin. Thanks -Dean
Minor upgrades d
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> Over this past weekend, the PostgreSQL Global Development Group packaged
> up and put onto our ftp server PostgreSQL v7.2.1 ... a bug fix release, it
> fixes a critical bug in v7.2:
> sequence counters will go backwards after a crash
It seems
> cash I/O improvements (Tom)
If it will change the I/O cash flow to more I than O, it will definitely be
a success... :-)
--
Kaare Rasmussen--Linux, spil,--Tlf:3816 2582
Kaki Datatshirts, merchandize Fax:3816 2501
Howitzvej 75
Over this past weekend, the PostgreSQL Global Development Group packaged
up and put onto our ftp server PostgreSQL v7.2.1 ... a bug fix release, it
fixes a critical bug in v7.2:
sequence counters will go backwards after a crash
Other fixes since v7.2 include:
Fix pgaccess kanji-coversion
Bradley McLean wrote:
>
> Patch against 7,2 submitted for comment.
>
> It's a little messy; I had some trouble trying to reconcile the code
> style of libpq which I copied from, and odbc.
>
> Suggestions on what parts look ugly, and or where to send this
> (is there a separate ODBC place?) are w
> So the work that would need to be done is asking the driver to request the
> timeout via "BEGIN WORK TIMEOUT 5"; getting the backend to parse that
> request and set the alarm on each query in that transaction; getting the
Well imho that interpretation would be completely unobvious.
My first g
On Monday 01 April 2002 20:18, Bruce Momjian wrote:
> Tom Lane wrote:>
> Agreed, only one timeout.
> ...
We have (at least) two ortogonal reasons why we want
to abort a long running transaction:
- The long running transaction might compute a result
we are not interesed anymore (because it j
We have a request from our customers to link
two database servers through the ISDN link.
We found the dblink in the contrib directory, and
it works ,but there is one big problem.
I'll try to explain it using the sample from
README.dblink:
SAMPLE:
create view myremotetable as select
dbl
68 matches
Mail list logo
