Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
>> No, I don't think so. It doesn't seem to be something that enough
>> people use to risk the change in behavior --- it might break something
>> that was working. But, if folks want it backported we can do it. It is
>> only a change to properl
> No, I don't think so. It doesn't seem to be something that enough
people use to risk the change in behavior --- it might break something
that was working. But, if folks want it backported we can do it. It is
only a change to properly do modulus for numeric.
Well, from my point of view it'
Log Message:
---
Add description for backend termination:
< cleaned up properly. A new signal is needed for safe termination.
> cleaned up properly. A new signal is needed for safe termination
> because backends must first do a query cancel, then exit once they
> have run the que
Log Message:
---
Here's a patch to do the following:
1. Rename spi_return_next to return_next.
2. Add a new test for return_next.
3. Update the expected output.
4. Update the documentation.
Abhijit Menon-Sen
Modified Files:
--
pgsql/doc/src/sgml:
plperl.sgml (r2.4
Log Message:
---
Code for SET/SHOW TIME ZONE with a fixed-interval timezone was not
prepared for HAVE_INT64_TIMESTAMP. Per report from Guillaume Beaudoin.
Tags:
REL8_0_STABLE
Modified Files:
--
pgsql/src/backend/commands:
variable.c (r1.105 -> r1.105.4.1)
Log Message:
---
Code for SET/SHOW TIME ZONE with a fixed-interval timezone was not
prepared for HAVE_INT64_TIMESTAMP. Per report from Guillaume Beaudoin.
Tags:
REL7_3_STABLE
Modified Files:
--
pgsql/src/backend/commands:
variable.c (r1.71.2.2 -> r1.71.2.3)
Log Message:
---
Code for SET/SHOW TIME ZONE with a fixed-interval timezone was not
prepared for HAVE_INT64_TIMESTAMP. Per report from Guillaume Beaudoin.
Tags:
REL7_4_STABLE
Modified Files:
--
pgsql/src/backend/commands:
variable.c (r1.88.2.1 -> r1.88.2.2)
Log Message:
---
Code for SET/SHOW TIME ZONE with a fixed-interval timezone was not
prepared for HAVE_INT64_TIMESTAMP. Per report from Guillaume Beaudoin.
Modified Files:
--
pgsql/src/backend/commands:
variable.c (r1.106 -> r1.107)
(http://developer.postgr
Log Message:
---
Add TODO.detail for 2phase commit:
> * Add two-phase commit [2phase]
Modified Files:
--
pgsql/doc:
TODO (r1.1550 -> r1.1551)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1550&r2=1.1551)
pgsql/doc/src/FAQ:
Log Message:
---
Add 2phase TODO.detail.
Added Files:
---
pgsql/doc/TODO.detail:
2phase (r1.3)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.detail/2phase?rev=1.3&content-type=text/x-cvsweb-markup)
pitr (r1.1)
(http://developer.pos
Log Message:
---
Replace the parser's namespace tree (which formerly had the same
representation as the jointree) with two lists of RTEs, one showing
the RTEs accessible by qualified names, and the other showing the RTEs
accessible by unqualified names. I think this is conceptually simpler
Log Message:
---
Add TODO.detail.
< logs
> logs [pitr]
130c130
< * Allow a warm standby system to also allow read-only queries
> * Allow a warm standby system to also allow read-only queries [pitr]
Modified Files:
--
pgsql/doc:
TODO (r1.1549 -> r1.1550)
Log Message:
---
Remove duplicate emails.
Modified Files:
--
pgsql/doc/TODO.detail:
wal (r1.6 -> r1.7)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.detail/wal.diff?r1=1.6&r2=1.7)
---(end of broadcast)--
Log Message:
---
Add TODO.detail for timezone:
< information, either zone name or offset from UTC
> information, either zone name or offset from UTC [timezone]
Modified Files:
--
pgsql/doc:
TODO (r1.1548 -> r1.1549)
(http://developer.postgresql.org/cvs
Log Message:
---
Add TODO.detail of standard timezone data type.
Added Files:
---
pgsql/doc/TODO.detail:
timezone (r1.1)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.detail/timezone?rev=1.1&content-type=text/x-cvsweb-markup)
-
Log Message:
---
Add pg_upgrade TODO.detail.
Added Files:
---
pgsql/doc/TODO.detail:
pg_upgrade (r1.1)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.detail/pg_upgrade?rev=1.1&content-type=text/x-cvsweb-markup)
---(end of br
Log Message:
---
Add TODO.detail:
> * Allow major upgrades without dump/reload, perhaps using pg_upgrade
> [pg_upgrade]
Modified Files:
--
pgsql/doc:
TODO (r1.1547 -> r1.1548)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1547&r2=
Log Message:
---
Add pg_dump TODO.detail for multiple -t / -n flags.
Modified Files:
--
pgsql/doc/TODO.detail:
pg_dump (r1.1 -> r1.2)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.detail/pg_dump.diff?r1=1.1&r2=1.2)
---(
Log Message:
---
Add pg_dump to TODO.detail.
Modified Files:
--
pgsql/doc:
TODO (r1.1546 -> r1.1547)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1546&r2=1.1547)
pgsql/doc/src/FAQ:
TODO.html (r1.53 -> r1.54)
(htt
Log Message:
---
Back out patch:
---
Tom Lane <[EMAIL PROTECTED]> writes:
> a_ogawa <[EMAIL PROTECTED]> writes:
> > It is a reasonable idea. However, the majority part of MemSet was not
> > able to be avoided by this
Log Message:
---
Add comment for multi-byte computation.
Modified Files:
--
pgsql/src/backend/parser:
parse_expr.c (r1.182 -> r1.183)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_expr.c.diff?r1=1.182&r2=1.183)
Log Message:
---
Allow kerberos name and username case sensitivity to be specified from
postgresql.conf.
---
Here's an updated version of the patch, with the following changes:
1) No longer uses "service name" as "
Log Message:
---
At 2005-05-21 20:18:50 +0530, [EMAIL PROTECTED] wrote:
>
> > The second issue is where plperl returns a large result set.
I have attached the following seven patches to address this problem:
1. Trivial. Replaces some errant spaces with tabs.
2. Trivial. Fixes the spellin
Log Message:
---
Tom Lane <[EMAIL PROTECTED]> writes:
> a_ogawa <[EMAIL PROTECTED]> writes:
> > It is a reasonable idea. However, the majority part of MemSet was not
> > able to be avoided by this idea. Because the per-tuple contexts are used
> > at the early stage of executor.
>
> Drat. W
Log Message:
---
Change expandRTE() and ResolveNew() back to taking just the single
RTE of interest, rather than the whole rangetable list. This makes
the API more understandable and avoids duplicate RTE lookups. This
patch reverts no-longer-needed portions of my patch of 2004-08-19.
Mod
Log Message:
---
Back out make_mkid change.
Modified Files:
--
pgsql/src/tools:
make_mkid (r1.9 -> r1.10)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/tools/make_mkid.diff?r1=1.9&r2=1.10)
---(end of broadcast)--
Log Message:
---
Improve readability of config location params by adding newline.
Modified Files:
--
pgsql/src/backend/utils/misc:
postgresql.conf.sample (r1.141 -> r1.142)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/misc/postgresql.
Log Message:
---
Add:
> * Allow pg_ctl to work properly with configuration files located outside
> the PGDATA directory
>
> pg_ctl can not read the pid file because it isn't located in the
> config directory but in the PGDATA directory. The solution is to
> allow pg_ctl to read a
Log Message:
---
Add description:
>
> O_DIRECT doesn't have the same media write guarantees as fsync, so it
> is in addition to the fsync method, not in place of it.
>
Modified Files:
--
pgsql/doc:
TODO (r1.1544 -> r1.1545)
(http://developer.postgresql
Christopher Kings-Lynne wrote:
> Is this a backport?
No, I don't think so. It doesn't seem to be something that enough
people use to risk the change in behavior --- it might break something
that was working. But, if folks want it backported we can do it. It is
only a change to properly do modul
Is this a backport?
Bruce Momjian wrote:
Log Message:
---
Fix NUMERIC modulus to properly truncate division in computation.
Division rounding was causing incorrect results. Test case:
test=> SELECT 12345678901234567890 % 123;
?column?
--
Log Message:
---
Fix NUMERIC modulus to properly truncate division in computation.
Division rounding was causing incorrect results. Test case:
test=> SELECT 12345678901234567890 % 123;
?column?
--
78
(1 row)
Was returning -45.
Mod
32 matches
Mail list logo
