Am Mittwoch, 12. Januar 2005 15:56 schrieb toczek:
I've made same updates and fixed some errors in file initdb-pl.po.
File is attached.
Installed.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 1:
Am Montag, 10. Januar 2005 01:46 schrieb toczek:
I've translated file libpq and as usually files attached goes :
Installed.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 8: explain analyze is your
Am Montag, 10. Januar 2005 02:21 schrieb toczek:
and another file has been translated ;].
Installed.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
A simple patch allow query output in psql PROMPT strings:
Index: prompt.c
===
RCS file: /projects/cvsroot/pgsql/src/bin/psql/prompt.c,v
retrieving revision 1.38
diff -U2 -r1.38 prompt.c
--- prompt.c1 Jan 2005 05:43:08 -
strk [EMAIL PROTECTED] writes:
A simple patch allow query output in psql PROMPT strings:
Why is this a good idea? Having a query implicitly executed during
every prompt will have a ton of bad side effects, for instance
prematurely freezing the query snapshot in SERIALIZABLE transactions.
The
On Fri, Jan 14, 2005 at 12:06:32PM -0500, Tom Lane wrote:
strk [EMAIL PROTECTED] writes:
A simple patch allow query output in psql PROMPT strings:
Why is this a good idea? Having a query implicitly executed during
every prompt will have a ton of bad side effects, for instance
prematurely
Hackers,
This patch fixes an obsolete comment.
--
Alvaro Herrera (alvherre[a]dcc.uchile.cl)
El realista sabe lo que quiere; el idealista quiere lo que sabe (Anónimo)
Index: executor/execMain.c
===
RCS file:
Alvaro Herrera [EMAIL PROTECTED] writes:
This patch fixes an obsolete comment.
Applied, thanks.
regards, tom lane
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Attached is a patch to allow the user to change the behavior of postgres with
reguards to case sensitivity on unquoted identifiers. This does not change
the default behavior of converting unquoted identifiers to lowercase, but
does allow (for instance, and I'm absolutly -not- pulling from
Opps! I have my logic backwards below. Those two SQL sets should be
set parser-ignore-case = true;
select Address_id from Address;
set parser-ignore-case = false;
select Address_id from Address;
On Friday 14 January 2005 02:51 pm, Michael W Mitton wrote:
Attached is a patch to allow the user
Michael W Mitton [EMAIL PROTECTED] writes:
Attached is a patch to allow the user to change the behavior of postgres with
reguards to case sensitivity on unquoted identifiers.
This patch has zero chance of being accepted. Please read the past
discussions in the pgsql-hackers' archives to find
Mark Kirkwood wrote:
Looking at option 2, it seems reasonable to add a trimmed trigger
example into the plpgsql examples section now, and leave the data
warehouse introductory stuff for its own chapter at some later stage.
Sorry about this -
A amendment so as not not require a SELECT from the
The recent change to pg_regress.sh has apparently broken testing on my
Windows machine - see
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=lorisdt=2005-01-15%2001:36:36
which contains this:
== pgsql.2544/src/test/regress/log/postmaster.log
===
LOG: could
Andrew Dunstan [EMAIL PROTECTED] writes:
The recent change to pg_regress.sh has apparently broken testing on my
Windows machine - see
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=lorisdt=2005-01-15%2001:36:36
which contains this:
Y'know, I wondered why windows wasn't listed in that
Mark Kirkwood [EMAIL PROTECTED] writes:
A amendment so as not not require a SELECT from the main table in the
trigger procedure. This makes the intent of the code more obvious, and
makes more sense within the context of the example.
Yeah, much better. Applied.
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
The recent change to pg_regress.sh has apparently broken testing on my
Windows machine - see
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=lorisdt=2005-01-15%2001:36:36
which contains this:
Y'know, I wondered why windows
Hackers,
This patches corrects the use of 0 as NULL in dllist.c, as reported by
sparse. There are still other places to be corrected.
Althought fairly trivial, it's not meant to be applied just now ...
--
Alvaro Herrera (alvherre[a]dcc.uchile.cl)
El que vive para el futuro es un iluso, y el
Andrew Dunstan [EMAIL PROTECTED] writes:
Tom Lane wrote:
What about the Cygwin port --- will it have the same issue? If so what
should we add?
No, Cygwin works OK - still have occasional issues with non-empty
tablespaces, but not this issue. The Cygwin environment itself emulates
unix
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
Tom Lane wrote:
What about the Cygwin port --- will it have the same issue? If so what
should we add?
No, Cygwin works OK - still have occasional issues with non-empty
tablespaces, but not this issue. The Cygwin
Andrew Dunstan [EMAIL PROTECTED] writes:
Tom Lane wrote:
Hm --- have you checked it since I changed the script?
yes. See
http://www.pgbuildfarm.org/cgi-bin/show_history.pl?nm=gibbonbr=HEAD
[ scratches head... ] Why isn't the #undef in pg_config_manual.h firing
on Cygwin?
Tom Lane said:
Andrew Dunstan [EMAIL PROTECTED] writes:
Tom Lane wrote:
Hm --- have you checked it since I changed the script?
yes. See
http://www.pgbuildfarm.org/cgi-bin/show_history.pl?nm=gibbonbr=HEAD
[ scratches head... ] Why isn't the #undef in pg_config_manual.h
firing on Cygwin?
Andrew Dunstan [EMAIL PROTECTED] writes:
Tom Lane said:
[ scratches head... ] Why isn't the #undef in pg_config_manual.h
firing on Cygwin?
But on Cygwin, WIN32 is only defined if windows.h has been included (See
previous discussion - I recall advocating NOT using WIN32 as a marker for
just
22 matches
Mail list logo
