David Rowley wrote:
> I propose we just remove the whole paragraph, and mention about
> the planning and estimated number of groups stuff in another new paragraph.
>
> I've attached a patch to this effect ...
s/In a worse case scenario/In the worst case scenario,/
Other than that, the phrasing i
Robert Haas wrote:
> +COUNT(*), each worker must compute subtotals which later must
> +be combined to produce an overall total in order to produce the final
> +answer. If the query involves a GROUP BY clause,
> +separate subtotals must be computed for each group seen by each paral
On January 27, 2017 07:08, Tom Lane wrote:
> ... The things I think are unique to the currency situation are: ...
Add the potential for regulatory requirements to change at any time - sort of
like timezone information. So no hard coded behavior.
rounding method/accuracy
storage precision
On Wed, Nov 16, 2016 at 6:43 AM, Robert Haas wrote:
> I think I was suggesting: One or more rows required by this query may
> already have been removed from "%s".
I keep reading that as "you have data corruption because something removed rows
that your query needs" rather than "this query took to
Magnus wrote:
> Just to be clear, you're suggesting 'One or more rows may have already been
> removed from "%s"?
Perhaps just 'This query attempted to access a page in "%s" that was modified
after the snapshot was acquired.'
On Tue, Nov 15, 2016 at 12:20 PM Magnus Hagander wrote:
> Is there value in showing the snapshot as well?
I don't think so. Knowing the relname let's you look at your report/job and
figure out if the access to that relation can be moved. Having the exact
snapshot version isn't going to change th
On Tue, Nov 15, 2016 at 10:30 AM, Tom Lane wrote:
>
> Kevin Grittner writes:
> > On Tue, Nov 15, 2016 at 3:38 AM, Magnus Hagander
> wrote:
> >> Is there a reason why we don't log which relation triggered the
> >> snapshot too old error when it happens?
>
> > I would probably not want to mess wi
Anastasia, et al,
This is a review of including_columns_9.7_v5.patch.
I looked through the commit fest list and this patch was interesting and I
wanted to try it.
I have used include columns on Microsoft SQL Server; DB2 for Linux, Unix,
Windows; and DB2 for z/OS.
After reading the e-mail disc
.. are some workloads where even larger settings ...
Regards,
Brad DeJong
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
_foo" is not a table
test=# create foreign table local_foo (id integer) server test_server options
(table_name 'foo');
CREATE FOREIGN TABLE
Brad
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
ikewise, has
> it always been true that -w is unnecessary? For other systems
> such as Mac OS X, we have recommendations covering quite ancient OS
> releases, and I don't see why we'd not hold the FreeBSD section to the
> same standard.
Well.. The man page appeared somewhe
On Tue, Jan 03, 2012 at 05:02:57PM -0500, Andrew Dunstan wrote:
>
>
> On 01/03/2012 04:49 PM, Brad Davis wrote:
> > Hi,
> >
> > I have a patch that improves the documentation for FreeBSD Kernel Tuning:
> >
> > - Show a # prompt instead of $ to indicate a r
/loader.conf, instead
of setting them manually in the loader.
I have put these in a github fork of the repo, but I am new to git. So I
apologize if this is incorrect.
https://github.com/so14k/postgres/commit/12c03bdb2967346e7ad9ce0bdd3db8dfcf81507e
Regards,
Brad Davis
--
Sent via pgsql-hackers
On Monday 18 January 2010 16:40:07 Takahiro Itagaki wrote:
> "Brad T. Sliger" wrote:
> > I tried to apply this patch to the latest version of PostgreSQL in git
> > (bbfc96e). Some of the patch did not apply. Please find attached the
> > output from patch. The f
On Tuesday 12 January 2010 01:06:22 Takahiro Itagaki wrote:
> Psql shows too many parentheses when it prints triggers with WHEN clause.
>
> postgres=# \d t1
> Table "public.t1"
> Column | Type | Modifiers
> +-+---
> c1 | integer |
> Triggers:
> mytrig AFTE
On Tuesday 06 October 2009 11:35:03 Roger Leigh wrote:
> On Tue, Oct 06, 2009 at 10:44:27AM +0100, Roger Leigh wrote:
> > On Mon, Oct 05, 2009 at 04:32:08PM -0400, Tom Lane wrote:
> > > Roger Leigh writes:
> > > > On Sun, Oct 04, 2009 at 11:22:27PM +0300, Peter Eisentraut wrote:
> > > >> Elsewhere
On Friday 02 October 2009 04:21:35 Roger Leigh wrote:
> On Wed, Sep 30, 2009 at 06:50:46PM -0400, Tom Lane wrote:
> > Roger Leigh writes:
> > >> On Wed, 2009-09-30 at 11:03 -0400, Andrew Dunstan wrote:
> > >>> Thinking about this some more, ISTM a much better way of approaching
> > >>> it would be
On Sunday 27 September 2009 19:03:33 Robert Haas wrote:
> On Sun, Sep 27, 2009 at 9:24 PM, Selena Deckelmann
>
> wrote:
> > Hi!
> >
> > On Wed, Sep 23, 2009 at 2:16 AM, Roger Leigh wrote:
> >> On Fri, Sep 18, 2009 at 11:30:05AM -0700, Sele
On Fri, 2009-06-05 at 15:50 -0400, Bruce Momjian wrote:
> Brad Nicholson wrote:
> > I've been kicking the tires on this a bit, and I've found an issue when
> > dealing with contrib/ (specifically dblink, although I haven't looked
> > around anymore).
> >
uld be nice. Even better would be a sanity check
added to prevent this.
--
Brad Nicholson 416-673-4106
Database Administrator, Afilias Canada Corp.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
> significant loss of usability going from 8.2 to 8.3, in the minds of
> many people.
I put my hand up as one of those people.
--
Brad Nicholson 416-673-4106
Database Administrator, Afilias Canada Corp.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql
ossible but normally it only happens
> line-by-line at worst. This must have something to do with the
> buffering behavior on stderr. Perhaps the difference is caused
> by a difference in where the postmaster's stderr originally pointed
> --- was this postmaster started in a differe
Tom Lane wrote:
> Brad Nicholson <[EMAIL PROTECTED]> writes:
>> It may or may not be the same issue, but for what it's worth, we've seen
>> the same sl_log_1 corruption on AIX 5.1 and 5.3
>
> Hm, on what filesystem, and what PG version(s)?
>
> I
Brad Nicholson wrote:
> Tom Lane wrote:
>> Marc Munro <[EMAIL PROTECTED]> writes:
>>> I'll get back to you with kernel build information tomorrow. We'll also
>>> try to talk to some kernel hackers about this.
>> Some googling turned up recent discu
Linux NFS code:
>
> http://threebit.net/mail-archive/linux-kernel/msg05313.html
> http://lkml.org/lkml/2006/3/1/381
>
> I don't know the kernel nearly well enough to guess if these are related
> ...
It may or may not be the same issue, but for what it's worth, we
04a30 in PostgresMain (argc=4, argv=0x202706b0,
username=0x20270620 "slony") at postgres.c:2877
#16 0x10036f70 in BackendFork (port=0x202a5c28) at postmaster.c:2564
#17 0x10036908 in BackendStartup (port=0x202a5c28) at postmaster.c:2207
#18 0x10034bb0 in ServerLoop () at postmaster.c:11
Oleg Bartunov wrote:
Joshua,
does RT has full support of PostgreSQL ?
It support's Postgres, but it uses a dynamic query builder that is
pretty brain dead. It only implements features that are cross DB
compatible. It comes up with some pretty ugly queries.
--
Brad Nicholson 416-673
./configure --enable-debug --with-perl
==
All 96 tests passed.
==
uname -a
Linux richard 2.6.5-7.111.19-smp #1 SMP Fri Dec 10 15:10:58 UTC 2004
x86_64 x86_64 x86_64 GNU/Linux
--
Brad Nicholson
Database Administrator, Afilias Canada Corp
AIX 5.1
I applied Bruce's patch, configured with --enable-thread-safety and
everything went smoothly.
==
All 96 tests passed.
==
Brad.
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands
Bruce Momjian wrote:
Brad Nicholson wrote:
OK, I assume you used --enable-thread-safety in configure.
Correct.
This should
have added some PTHREAD link flags to your libpq build, and those
settings should have followed the libpq library into your pg_ctl link
line.
Would you look
Bruce Momjian wrote:
Brad Nicholson wrote:
I tried compliling v8 beta 5 (grabbed from cvs on Friday) on AIX 5.1.
It fails during the make
make[4]: Entering directory
`/opt/OXRS/Sources/pgsql-HEAD/src/interfaces/libpq'
make[4]: Nothing to be done for `all'.
make[4]: Leaving direct
: Leaving directory `/opt/OXRS/Sources/pgsql-HEAD/src/bin/pg_ctl'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/opt/OXRS/Sources/pgsql-HEAD/src/bin'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/opt/OXRS/Sources/pgsql-HEAD/src'
make: *** [all] Error 2
Brad.
: .pthread_mutex_unlock
ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more
information.
collect2: ld returned 8 exit status
make[3]: *** [pg_ctl] Error 1
Brad.
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL
repareStatement("select
pg_set_client_encoding('LATIN5'); ");
rs = pStmt.executeQuery();
I can set the client encoding from within psql by /encoding LATIN5 but
not sure how to execute something like this from java. Any help would
be greatly appreciated.
Thanks,
Brad
-
35 matches
Mail list logo
