this, but
they also included comments pertaining to the branch, so I assumed
the braces were appropriate to clarify the branch extent.
Michael Glaesemann
grzm seespotcode net
---(end of broadcast)---
TIP 1: if posting/reading through Usenet
instant in time.
Michael Glaesemann
grzm seespotcode net
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through
the tuple is marked LP_DELETE?
Vacuum
--
Vacuum prunes all HOT chains, and removes any LP_DELETEd tuples,
making the space available for any use.
In the case of a fragmented row, am I right to assume vacuum reclaims
all space up to the next (live) tuple?
Michael Glaesemann
grzm seespotcode
.
I'm curious as to know how often these are used at all. I think I may
have used createuser once and used to use createlang, but I can't
recall ever using the others.
Michael Glaesemann
grzm seespotcode net
---(end of broadcast)---
TIP 9
of these binaries really
should be namespaced in some way. The current just too generic to be
throwing into a bin/ directory in my opinion.
Michael Glaesemann
grzm seespotcode net
---(end of broadcast)---
TIP 4: Have you searched our list
consistent.
Michael Glaesemann
grzm seespotcode net
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
) and internally reserve a
certain amount off for whatever headroom might be required. It's more
common for users to see a value range from 0 to 1 rather than 0 to 0.9.
Michael Glaesemann
grzm seespotcode net
---(end of broadcast)---
TIP 3: Have you
this isn't a good idea, but are there other places
where there might be gotchas for the unwary, such as DISTINCT without
ORDER BY or (for an unrelated example) UNION versus UNION ALL? How
many of these types of messages would be useful?
Michael Glaesemann
grzm seespotcode net
BY?
Michael Glaesemann
grzm seespotcode net
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
such as
#define #define USECS_PER_SEC INT64CONST(100)
I'd like to work up a patch that would add similar macros for
datetime.c, in particular using the INT64CONST construction where
appropriate. Thoughts?
Michael Glaesemann
grzm seespotcode net
---(end of broadcast
future. Or maybe I should learn Spanish :)
Michael Glaesemann
grzm seespotcode net
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
). If there is interest I can translate
the
docs, but I have posted the script in these lists before and got no
much
of an interest. Michael Glaesemann did find it useful when I
showed it
to him in the summit, though.
Ooo! Nifty! I'll have to check out what's changed. I still use this
script
default behavior.
Would it make more sense to have phrase it in the positive sense?
i.e., --enable-floating-point-datetimes? I guess that's a bit longer,
but it says what you're doing, rather than what you're *not* doing.
Michael Glaesemann
grzm seespotcode net
---(end
. I tried to be conscientious
about my formatting, but some SGML bugs may have crept in.
Thanks!
Michael Glaesemann
grzm myrealbox com
Index: doc/src/sgml/ref/create_constraint.sgml
===
RCS file: /projects/cvsroot/pgsql/doc/src/sgml
I've posted a 6.5kB patch (as an attachment) three times over the
past few days but haven't seen it hit the lists. Checking to see if
this goes through.
Michael Glaesemann
grzm seespotcode net
---(end of broadcast)---
TIP 6: explain analyze
On Sep 5, 2006, at 19:16 , Michael Meskes wrote:
On Mon, Sep 04, 2006 at 11:54:42PM +0900, Michael Glaesemann wrote:
The pg_regress.sh script for ecpg regression tests checks to make
sure the port number is between 1024 and 65535. If it isn't, it uses
65432. (c310-315. This is the same
unsure we want to do that. Right
now, this will show 25:00:00.
Updated patch that uses TSROUND for partial month and days. Michael
says the tests look good on his system. I think we are done with this
bug. :-)
Please find attached regression tests for this patch.
Michael Glaesemann
grzm
to the original
port number. Passes both the standard regression tests and, more
importantly, those for ecpg, with normal and abnormally high port
numbers.
Michael Glaesemann
grzm seespotcode net
Index: src/interfaces/ecpg/test/pg_regress.sh
On Sep 1, 2006, at 9:32 , Tom Lane wrote:
Michael Glaesemann [EMAIL PROTECTED] writes:
On Sep 1, 2006, at 9:12 , Tom Lane wrote:
I agree that this seems like an oversight in the original
months/days/seconds patch, rather than behavior we want to keep.
But is DecodeInterval the only place
remainder separately?
Michael Glaesemann
grzm seespotcode net
---(end of broadcast)---
TIP 6: explain analyze is your friend
days component to time. I.e., 9.99 mon is 9 mon 29.7 days, rather
than 9 mon 29 days 60480 sec.
Michael Glaesemann
grzm seespotcode net
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http
On Sep 3, 2006, at 20:00 , Michael Glaesemann wrote:
On Sep 1, 2006, at 9:32 , Tom Lane wrote:
Michael Glaesemann [EMAIL PROTECTED] writes:
On Sep 1, 2006, at 9:12 , Tom Lane wrote:
I agree that this seems like an oversight in the original
months/days/seconds patch, rather than behavior
On Sep 4, 2006, at 9:41 , Tom Lane wrote:
This patch fails to apply --- looks like whitespace got mangled in
transit. Please resend as an attachment.
Please let me know if you have any problems with this one.
Michael Glaesemann
grzm seespotcode net
10interval_input_0904T0855+0900.diff
is in minutes/seconds, not hours.
I was sure it was more wrong than that the first time I saw it, but
looks like I can't be sure of anything today :(. I need more sleep.
Sorry for the noise on this one.
Off work now, so I'm back at it.
Michael Glaesemann
grzm seespotcode net
the known issues
with the interval code in one place. Probably too ambitious for
September 1.
Is it worth looking into the overflow and subtraction issues for 8.2?
It seems to me they're bugs rather than features. Or are these 8.3
since it's so late?
Michael Glaesemann
grzm seespotcode net
good, I'll add the
examples we've been using to the regression tests.
Michael Glaesemann
grzm seespotcode net
Index: src/backend/utils/adt/timestamp.c
===
RCS file: /projects/cvsroot/pgsql/src/backend/utils/adt/timestamp.c,v
Please ignore the patch I just sent. Much too quick with the send
button.
Michael Glaesemann
grzm seespotcode net
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your
-
integer-datetimes is pretty broken with this patch.
Michael Glaesemann
grzm seespotcode net
-- test queries
select interval '41 mon 12 days 360:00' * 0.3 as product_a
, interval '-41 mon -12 days +360:00' * 0.3 as product_b
, interval '-41 mon 12 days 360:00' * 0.3 as product_c
On Sep 1, 2006, at 9:12 , Tom Lane wrote:
Michael Glaesemann [EMAIL PROTECTED] writes:
I came across some behavior that seems counterintuitive to me:
test=# select '1.5 mon'::interval;
interval
-
1 mon 360:00:00
(1 row)
With the time/day/month interval struct
?
--
-3 days -14:23:60.00
(1 row)
I think some kind of rounding needs to be done to the day
contribution as well. I'm continuing to work on it, but wanted to get
this out there.
Michael Glaesemann
grzm seespotcode net
---(end of broadcast
?
Thanks!
Michael Glaesemann
grzm seespotcode net
---8-
Index: src/backend/utils/adt/timestamp.c
===
RCS file: /projects/cvsroot/pgsql/src/backend/utils/adt/timestamp.c,v
retrieving revision 1.165
diff -c -r1.165 timestamp.c
*** src
| 1 year 6 days -122:23:60.00 | -1 years -6
days +122:24:00 | -1 years -12 days -122:23:60.00
(1 row)
The quotients look fine, but I'm wondering if another set of rounding
is needed to bump those -122:23:60.00 to -122:24:00 in product_b and
product_d.
Michael Glaesemann
grzm seespotcode net
tonight.
Michael Glaesemann
grzm seespotcode net
Index: src/backend/utils/adt/timestamp.c
===
RCS file: /projects/cvsroot/pgsql/src/backend/utils/adt/timestamp.c,v
retrieving revision 1.165
diff -c
this.
Patch attached. It also fixes a regression test output too.
Thanks for the patch. I'll look at it more closely tonight.
Michael Glaesemann
grzm seespotcode net
---(end of broadcast)---
TIP 5: don't forget to increase your free space map
in the lines including USECS_PER_DAY and USECS_PER_MONTH, and my
inexperience with C and gdb is getting the best of me right now
(though I'm still plugging away: ).
Michael Glaesemann
grzm seespotcode net
8---
? CONFIGURE_ARGS
? datetime.patch
? timestamp.patch
? src/backend
.
I think this is a behavior changing bug fix, as it was the intention
of the Interval struct change to treat days and time differently.
This patch brings the DecodeInterval function more in line with that
intention.
Thanks for your consideration.
Michael Glaesemann
grzm seespotcode net
it no longer (?) is. That brings
me back to the idea of VALUES deserving its own reference page.
I wonder how soon pretty much the entire SQL spec will be duplicated
in the PostgreSQL documentation. :)
Michael Glaesemann
grzm seespotcode net
---(end of broadcast
On Aug 4, 2006, at 9:42 , Gavin Sherry wrote:
... with update? I associate it very closely with INSERT. After all,
INSERT is the only statement where we've had VALUES as part of the
grammar.
Of course! Thanks for catching the glitch. I must have a bad RAM chip.
Michael Glaesemann
grzm
or Oracle-specific?
Michael Glaesemann
grzm myrealbox com
---(end of broadcast)---
TIP 6: explain analyze is your friend
a bit more. (I haven't been sleeping well
recently.)
Michael Glaesemann
grzm myrealbox com
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so
On Feb 21, 2006, at 14:24 , Tom Lane wrote:
Michael Glaesemann [EMAIL PROTECTED] writes:
Most of this is way above my head, but I'm trying to follow along:
Right, it's whatever is the sort key for this particular sort.
Thanks, Tom. I think I may actually be starting to understand
on (a.aa = c.cc);
ERROR: invalid reference to FROM-clause entry for table a
HINT: There is an entry for a, but it cannot be referenced from
this part of the query.
For clarity, I'd rewrite this hint as
There is an entry for table a, ...
Michael Glaesemann
grzm myrealbox com
On Nov 17, 2005, at 11:51 , Christopher Kings-Lynne wrote:
Including objects that already have CREATE OR REPLACE?
I assume so - CREATE OR REPLACE doesn't drop things - only creates
or replaces them.
Of course. Silly me :)
Michael Glaesemann
grzm myrealbox com
...
Including objects that already have CREATE OR REPLACE?
Michael Glaesemann
grzm myrealbox com
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
DROP
TABLE. It reminds me of the old behavior of outputting COMMIT even in
the case of transaction failure. I find the current behavior of
outputting ROLLBACK in the case of transaction failure more useful.
Michael Glaesemann
grzm myrealbox com
---(end of broadcast
me know.
I've included the diff in the email as well (below) for ease of review.
Michael Glaesemann
grzm myrealbox com
Index: doc/src/sgml/func.sgml
===
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/func.sgml,v
retrieving revision
it's kind of frustrating that
none of us have been able to hit on a term that accurately and
succinctly describes it.)
Michael Glaesemann
grzm myrealbox com
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send
()
pg_table_support_size()
pg_relation_extensions_size()
pg_relation_support_size()
pg_relation_extended_size()
My two yen... if that :)
Michael Glaesemann
grzm myrealbox com
---(end of broadcast)---
TIP 8: explain analyze is your friend
out, such as #define SIZEOF_INTERVAL 16 to make
the code a bit more robust (albeit just a little). Is this a
reasonable change?
Michael Glaesemann
grzm myrealbox com
interval_day.diff
Description: Binary data
---(end of broadcast)---
TIP 3
should be applied.
Thanks!
Michael Glaesemann
grzm myrealbox com
On Jun 5, 2005, at 9:17 AM, Bruce Momjian wrote:
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
It will be applied as soon as one of the PostgreSQL
'UTC':
CREATE FUNCTION to_timestamp (double precision)
returns timestamptz
language sql as '
select (
(\'epoch\'::timestamptz + $1 * \'1 second\'::interval)
at time zone \'UTC\'
) at time zone \'UTC\'
';
Michael Glaesemann
grzm myrealbox com
to_timestamp
On Nov 15, 2004, at 3:35 PM, Neil Conway wrote:
(-- might be considered an en dash, but AFAIK it is incorrect
to use an en dash to designate a parenthetical comment anyway).
Then again, wouldn't parentheses be the appropriate punctuation for a
parenthetical comment? :P
Michael Glaesemann
grzm
of something else.
Michael Glaesemann
grzm myrealbox com
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
1976-05-05 14:00:00+09
(1 row)
If regression tests are required, I will produce some. I'd appreciate
any pointers as to what to look for, as they would be my first attempt
at writing regression tests.
Regards
Michael Glaesemann
grzm myrealbox com
to_timestamp.diff
Description
a
FROM_UNIXTIME(integer, format) function that I really don't think would
be needed. Using a different syntax would call attention to this
difference.
Another idea would be to overload TO_TIMESTAMP to take a single double
precision float parameter rather than two text parameters.
Michael Glaesemann
grzm
appreciated.
Michael Glaesemann
grzm myrealbox com
func.sgml.diff
Description: Binary data
pg_proc.h.diff
Description: Binary data
---(end of broadcast)---
TIP 8: explain analyze is your friend
is being raised. I'd think
something as simple as
NOTICE: foreign key constraint 'constrname' will require a cross-type
conversion
similar to
NOTICE: CREATE TABLE / UNIQUE will create implicit index
foox_interesting_key for table foox
Michael Glaesemann
grzm myrealbox com
Below is a patch to provide a few links between the former
administrator's guide and appropriate reference pages.
Michael Glaesemann
grzm myrealbox com
Index: backup.sgml
===
RCS file: /projects/cvsroot/pgsql-server/doc/src/sgml
58 matches
Mail list logo