It's showing the apache page.
Chris
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cle
On Mon, 28 Jul 2003 04:27 pm, [EMAIL PROTECTED] wrote:
> Just part of the baptism of fire for a newbie, I guess. :-)
I've found the learning curve pretty steep too. Is it worth putting together
some of these 'gotchas' into a neophyte-developer-FAQ?
As a side note: anyone else noticed that devel
> > Yep, that solved both the make clean and the coredump problems.
> > Is that piece of information in the developers FAQ anywhere?
>
> It's in the "how to use CVS" instructions ...
So it is. I probably read that before I got CVS working here, and it
isn't mentioned (or that section of the docs
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I have only been running nightly paralell regression runs since June 27,
> so it is possible that the paralell regression was broken in February,
> fixed in May, then broken some time after that.
Any further progress on this?
My best theory at the momen
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> Just saw these:
> #default_transaction_isolation = 'read committed'
> #default_transaction_read_only = false
> Does the second option control the new read only transaction mode?
Yes.
> I thought 'read only' was just a new level of transactio
[EMAIL PROTECTED] writes:
>> I suspect you forgot "-d" in your cvs update commands. You really need
>> both -d and -P to make cvs update behave reasonably ... I have no idea
>> why they are not the default behavior.
> Yep, that solved both the make clean and the coredump problems.
> Is that piece
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
On Mon, 28 Jul 2003, Christopher Kings-Lynne wrote:
> Just saw these:
>
> #default_transaction_isolation = 'read committed'
> #default_transaction_read_only = false
>
> Does the second option control the new read only transaction mode? I
> thought 'read only' was just a new level of transaction
Just saw these:
#default_transaction_isolation = 'read committed'
#default_transaction_read_only = false
Does the second option control the new read only transaction mode? I
thought 'read only' was just a new level of transaction isolation (ie. one
of the 4 sql standard ones), so why does it nee
Just a slight nitpick, shouldn't this line:
# - Previous Postgres Versions -
Be this:
# - Previous PostgreSQL Versions -
Chris
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining colu
> [EMAIL PROTECTED] writes:
> > Make clean fails on an up-to-date CVS (as of 2:40 PM CDT on Sunday).
>
> > make: *** tsearch2: No such file or directory. Stop.
>
> I suspect you forgot "-d" in your cvs update commands. You really need
> both -d and -P to make cvs update behave reasonably ... I
Tom Lane wrote:
Joe Conway may already have written something like this --- look in his
contrib modules.
I did write the function, but it isn't in any of the contrib modules.
Here's a link to the thread:
http://archives.postgresql.org/pgsql-hackers/2002-12/msg00453.php
It was never committed due to
On Mon, 28 Jul 2003, Christopher Kings-Lynne wrote:
> > I'm declaring victory and going home ;-). If anyone else would like
> > to make a cleanup pass over the error message texts, be my guest.
>
> You're a legend, Tom. We thank you :)
I agree. I gave a talk to an Australian unix user group on
> I'm declaring victory and going home ;-). If anyone else would like
> to make a cleanup pass over the error message texts, be my guest.
You're a legend, Tom. We thank you :)
Chris
---(end of broadcast)---
TIP 1: subscribe and unsubscribe comma
I'm declaring victory and going home ;-). If anyone else would like
to make a cleanup pass over the error message texts, be my guest.
regards, tom lane
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
[EMAIL PROTECTED] writes:
> Make clean fails on an up-to-date CVS (as of 2:40 PM CDT on Sunday).
> make: *** tsearch2: No such file or directory. Stop.
I suspect you forgot "-d" in your cvs update commands. You really need
both -d and -P to make cvs update behave reasonably ... I have no idea
w
ivan <[EMAIL PROTECTED]> writes:
> declaration is setof record array_to_setof ( anyarray);
> i trayed created it like "any" array_to_setof( anyarray) but i had problem
> with select. i also trying write setof_to_array as aggregate, but i have
> problem with returns type , because aggregate cat hav
The following lines are from readme file present in the
\src\backend\storage\lmgr folder of postgresql
"If we are setting a table level lock
Both the blockId and tupleId (in an item pointer this is called
the position) are set to invalid, if it is a page level lock the
blockId is valid, while the
Sorry, wrong list...
On Sun, 27 Jul 2003 14:37:59 -0600
Robert Creager <[EMAIL PROTECTED]> said something like:
>
> Hey Guys,
>
> I'm working on translating my system to use pg_sphere. The question I
> have, which I think would make a good FAQ entry (or section is usage
> example?), is that I
hi :>
i wrote function to change array to setof record, because better is
working with tuples .
http://www.psycho.pl/public/src/pgsql/array.tar.bz2
i will very glade when you check this , because im afraid thed i make same
mistakes .. (if its good ist could be added to contrib/array as one more
"Tom Lane" <[EMAIL PROTECTED]> writes:
> "Mendola Gaetano" <[EMAIL PROTECTED]> writes:
> > Is once-in-a-while but always at 00 minutes. This select is performed
each
> > 20 minutes and
> > the core happen always at 00 never at 20 and never at 40!
>
> Now that is very interesting ... why would that
Hey Guys,
I'm working on translating my system to use pg_sphere. The question I
have, which I think would make a good FAQ entry (or section is usage
example?), is that I have a C language trigger function. How do I use
spoint (and other types) internal to that set of functions?
Note that I am
"Mendola Gaetano" <[EMAIL PROTECTED]> writes:
> Is once-in-a-while but always at 00 minutes. This select is performed each
> 20 minutes and
> the core happen always at 00 never at 20 and never at 40!
Now that is very interesting ... why would that be?
Could we see the definition of this view?
>
More problems with the latest CVS on FreeBSD:
make[3]: Leaving directory `/home/nolan/beta/pgsql/contrib/spi'
/bin/sh ./pg_regress --temp-install --top-builddir=../../.. --schedule=./paralle
l_schedule --multibyte=SQL_ASCII
== removing existing temp installation==
=
From: "Tom Lane" <[EMAIL PROTECTED]>
> "Mendola Gaetano" <[EMAIL PROTECTED]> writes:
> > From: "Tom Lane" <[EMAIL PROTECTED]>
> >> I suspect some form of
> >> data corruption in the pg_rewrite row(s) for this table. Do you
> >> see any misbehavior when you do
> >>
> >> select * from pg_rewrite whe
Make clean fails on an up-to-date CVS (as of 2:40 PM CDT on Sunday).
Here's the final part of the output:
make[2]: Leaving directory `/home/nolan/beta/pgsql/contrib/tablefunc'
make[2]: Entering directory `/home/nolan/beta/pgsql/contrib/tips'
make[2]: Nothing to be done for `clean'.
make[2]: Leavi
Sorry if I didn't mention it before, but this was on FreeBSD.
--
Mike Nolan
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
miscinit.c part of patch applied. Thanks.
The other part Tom already addressed.
---
Lee Kindness wrote:
Content-Description: message body text
> Tom, happier with the attached patch?
>
> I'd have to disagree with regar
"Mendola Gaetano" <[EMAIL PROTECTED]> writes:
> From: "Tom Lane" <[EMAIL PROTECTED]>
>> I suspect some form of
>> data corruption in the pg_rewrite row(s) for this table. Do you
>> see any misbehavior when you do
>>
>> select * from pg_rewrite where ev_class = 'v_psl_package_info'::regclass
> Al
From: "Tom Lane" <[EMAIL PROTECTED]>
> "Mendola Gaetano" <[EMAIL PROTECTED]> writes:
> > The process killed made always the same select ( with different
> > id_package ):
>
> > SELECT id_publisher, publisher_name, id_package, package_name
> > FROM v_psl_package_info
> > WHERE id_package = 177;
>
"Mendola Gaetano" <[EMAIL PROTECTED]> writes:
> The process killed made always the same select ( with different
> id_package ):
> SELECT id_publisher, publisher_name, id_package, package_name
> FROM v_psl_package_info
> WHERE id_package = 177;
> (gdb) where
> #0 0x08171fdd in RelationBuildRuleLo
Bruce Momjian <[EMAIL PROTECTED]> writes:
> That is a very good guess. All the errors seem related to the parser.
No, I don't think bison's got anything to do with it. AFAICS all the
reported failures look more like syscache-level problems. I'm betting
on a locking issue. It'll be easier to fi
Bruce Momjian <[EMAIL PROTECTED]> writes:
> This patch no longer applies cleanly. The call is now:
> freeaddrinfo_all(hint.ai_family, addrs);
> Would you please submit a new patch, or is it no longer required?
That part of the patch is not needed (it is the same as what I changed,
excep
33 matches
Mail list logo
