- 23 Apr, 1997 6 commits
-
-
Vadim B. Mikheev authored
-
Vadim B. Mikheev authored
2. vacuum() call changed (ANALYZE).
-
Vadim B. Mikheev authored
2. New VACUUM syntax (ANALYZE ...).
-
Vadim B. Mikheev authored
2. VacuumStmt changed (for VACUUM ANALYZE...).
-
Vadim B. Mikheev authored
-
Marc G. Fournier authored
Subject: Re: [PATCHES] SET DateStyle patches On Tue, 22 Apr 1997, Thomas Lockhart wrote: > Some more patches! These (try to) finish implementing SET variable TO value > for "DateStyle" (changed the name from simply "date" to be more descriptive). > This is based on code from Martin and Bruce (?), which was easy to modify. > The syntax is > > SET DateStyle TO 'iso' > SET DateStyle TO 'postgres' > SET DateStyle TO 'sql' > SET DateStyle TO 'european' > SET DateStyle TO 'noneuropean' > SET DateStyle TO 'us' (same as "noneuropean") > SET DateStyle TO 'default' (current same as "postgres,us") > > ("european" is just compared for the first 4 characters, and "noneuropean" > is compared for the first 7 to allow less typing). > > Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid. > > My mods also try to implement "SHOW variable" and "RESET variable", but > that part just core dumps at the moment. I would guess that my errors > are obvious to someone who knows what they are doing with the parser stuff, > so if someone (Bruce and/or Martin??) could have it do the right thing > we will have a more complete set of what we need. > > Also, I would like to have a floating point precision global variable to > implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for > float8 and float4, but I don't know how to do that for integer types rather > than strings. If someone is fixing the SHOW and RESET code, perhaps they can > add some hooks for me to do the floats while they are at it. > > I've left some remnants of variable structures in the source code which > I did not use in the interests of getting something working for v6.1. > We'll have time to clean things up for the next release...
-
- 22 Apr, 1997 6 commits
-
-
Marc G. Fournier authored
Subject: [PORTS] Configure for DEC-Alpha Configure script properly detects alpha-dec-osf4.0 machine, but sets a default GENERIC template for it. I modified tempplate/.similar to add alpha-dec-osf4.0=alpha. Then configure properly set the template to alpha.
-
Marc G. Fournier authored
type check in numutils.c:ftoa() Pointed out by: "Martin J. Laubach" <mjl@emsi.priv.at>
-
Marc G. Fournier authored
Subject: [PATCHES] Patch for configure.in to not ask for CASSERT The following patch defaults to CASSERT, so it doesn't ask you. You can still use --enable-cassert and --disable-cassert to do it explicitly. Default: disabled
-
Marc G. Fournier authored
Subject: [PATCHES] date/time timezone patches (mail bounced?) Here are some hacks to get timezone behavior for the various time data types to be compatible with v6.0. Although we have some hooks already installed to get timezone info from the client to the server, it still isn't clear if that can correctly transfer enough timezone info to make the behavior the same as if timezone info were derived from the server as is now the case. We certainly won't resolve it in a day, so I think we are stuck with server-only timezones for v6.1.
-
Marc G. Fournier authored
OK, here are a passel of patches for the geometric data types. These add a "circle" data type, new operators and functions for the existing data types, and change the default formats for some of the existing types to make them consistant with each other. Current formatting conventions (e.g. compatible with v6.0 to allow dump/reload) are supported, but the new conventions should be an improvement and we can eventually drop the old conventions entirely. For example, there are two kinds of paths (connected line segments), open and closed, and the old format was '(1,2,1,2,3,4)' for a closed path with two points (1,2) and (3,4) '(0,2,1,2,3,4)' for an open path with two points (1,2) and (3,4) Pretty arcane, huh? The new format for paths is '((1,2),(3,4))' for a closed path with two points (1,2) and (3,4) '[(1,2),(3,4)]' for an open path with two points (1,2) and (3,4) For polygons, the old convention is '(0,4,2,0,4,3)' for a triangle with points at (0,0),(4,4), and (2,3) and the new convention is '((0,0),(4,4),(2,3))' for a triangle with points at (0,0),(4,4), and (2,3) Other data types which are also represented as lists of points (e.g. boxes, line segments, and polygons) have similar representations (they surround each point with parens). For v6.1, any format which can be interpreted as the old style format is decoded as such; we can remove that backwards compatibility but ugly convention for v7.0. This will allow dump/reloads from v6.0. These include some updates to the regression test files to change the test for creating a data type from "circle" to "widget" to keep the test from trashing the new builtin circle type.
-
Vadim B. Mikheev authored
-
- 21 Apr, 1997 4 commits
-
-
Marc G. Fournier authored
-
Vadim B. Mikheev authored
-
Vadim B. Mikheev authored
-
Vadim B. Mikheev authored
-
- 20 Apr, 1997 1 commit
-
-
Marc G. Fournier authored
the last week on Hackers...(A coulpe of clippings of the final verdict are included below + the diff). From: Wayde Nie <niew@phoenix.cis.mcmaster.ca>
-
- 18 Apr, 1997 9 commits
-
-
Marc G. Fournier authored
--with-compiler=xlc Requested by: Darren King <aixssd!darrenk@abs.net>
-
Marc G. Fournier authored
Subject: [HACKERS] Another patch to configure.in I heard very little in objections/approvals to defaulting some of the parameters to configure. Enclosed is a patch to configure.in which removes the questions for PGPORT USE_LOCALE NOHBA By default (i.e. assuming you don't put anything extra in the configure command line), it assumes PGPORT=5432, USE_LOCAL=no and NOHBA=no (i.e. HBA is turned on) --with-pgport=PGPORT_NO Over-rides the PGPORT value --enable-locale enables USE_LOCALE --disable-hba disables HBA Just for completeness: --prefix=BASEDIR Defaults to /usr/local/pgsql --with-template=TEMPLATE Defaults to asking you
-
Vadim B. Mikheev authored
-
Vadim B. Mikheev authored
added to WriteBuffer(), FlushBuffer(), WriteNoReleaseBuffer().
-
Vadim B. Mikheev authored
building.
-
Vadim B. Mikheev authored
static const char *num_word(Cash value); moved to cash.c. 2. 'extern ' added to funcs prototypes.
-
Vadim B. Mikheev authored
static const char *num_word(Cash value); moved here from cash.h
-
Vadim B. Mikheev authored
blocks transfferes.
-
Vadim B. Mikheev authored
#ifdef USE_LOCALE added.
-
- 17 Apr, 1997 5 commits
-
-
Marc G. Fournier authored
Subject: [PATCHES] 970417: some large object patches Two patches here, made against 970417. Both have to do with large objects: 1. lobjfuncs was not initialized in PQconnectdb. This causes failure later if large objects are used. (Someone already caught this error in PQsetdb.) 2. Postgres functions lo_import and lo_export sometimes produce garbage for the file names because the filename strings aren't always terminated by \0. (VARDATA isn't necessarily null terminated.)
-
Marc G. Fournier authored
Subject: [PATCHES] 970417: two more patches for large objects Here are two more patches: 1. pg_getint doesn't properly set the status flag when calling pqGetShort or pqGetLong. This is required when accessing large objects via libpq. This, combined with problem 1 above causes postgres to crash when postgres tries to print out the message that the status was not good. 2. ExceptionalCondition crashes when called with detail = NULL. This patch prevents dereferencing the NULL.
-
Marc G. Fournier authored
Subject: [HACKERS] Patch: set date to euro/us postgres/iso/sql Here a patch that implements a SET date for use by the datetime stuff. The syntax is SET date TO 'val[,val,...]' where val is us (us dates), euro (european dates), postgres, iso or sql. Thomas is working on the integration in his datetime module. I just needed to get the patch out before it went stale :)
-
Marc G. Fournier authored
a -D<datadir> option
-
Vadim B. Mikheev authored
table. The table name is de-allocated by the CommitTransactionCommand() in vc_init() before it is copied in VacRel.data and sometimes this causes a SIGSEGV. My patch simply moves the strcpy before vc_init. Submitted by Massimo Dal Zotto <dz@cs.unitn.it>.
-
- 16 Apr, 1997 5 commits
-
-
Marc G. Fournier authored
-
Vadim B. Mikheev authored
-
Vadim B. Mikheev authored
-
Vadim B. Mikheev authored
index tuple (logical position within A LEVEL). bti_oid & bti_dummy taken off from BTItemData. 2. Fix for multi-column indices (nbtsearch.c): _bt_binsrch() - for searches on internal pages having keysize < number of attrs we point at the last item < the scankey, not at the first item = the scankey; _bt_moveright() - if keysize < number of attrs we compare scankey with _last_ item on current page to decide should we move right or not.
-
Vadim B. Mikheev authored
index tuple (logical position within A LEVEL). bti_oid & bti_dummy taken off from BTItemData.
-
- 15 Apr, 1997 4 commits
-
-
Marc G. Fournier authored
-
Marc G. Fournier authored
-
Marc G. Fournier authored
instead of as a -D
-
Marc G. Fournier authored
-