On 11/30/2010 10:09 PM, Tom Lane wrote:
Josh Berkusj...@agliodbs.com writes:
Apparently, testing for O_DIRECT at compile time isn't adequate. Ideas?
We should wait for the outcome of the discussion about whether to change
the default wal_sync_method before worrying about this.
2010/11/25 Shigeru HANADA han...@metrosystems.co.jp:
Hi hackers,
Attached is a patch that adds core functionality of SQL/MED. This
patch provides:
SQL/MED - file_fdw : FDW for external PostgreSQL
SEL/MED - postgresql_fdw : FDW for server-side file (CSV, TEXT)
I've tried
I have played around a little more, and think I found a problem.
If given enough time, an unlogged table makes it to disk, and a restart wont
clear the data. If I insert a bunch of stuff, commit, and quickly restart PG,
it table is cleared. If I let it sit for a while, it stays.
Based on
(2010/11/30 21:26), Simon Riggs wrote:
On Mon, 2010-11-29 at 21:37 -0500, Josh Kupershmidt wrote:
I still see little reason to make LOCK TABLE permissions different for
column-level vs. table-level UPDATE privileges
Agreed.
This is the crux of the debate. Why should this inconsistency
Andrew Dunstan and...@dunslane.net writes:
On 11/30/2010 10:09 PM, Tom Lane wrote:
We should wait for the outcome of the discussion about whether to change
the default wal_sync_method before worrying about this.
we've just had a significant PGX customer encounter this with the latest
Jeff Janes wrote:
Have you tested out this absorb during syncing phase code without
the sleep between the syncs?
I.e. so that it still a tight loop, but the loop alternates between
sync and absorb, with no intentional pause?
Yes; that's how it was developed. It helped to have just the
On 11/28/10, Robert Haas robertmh...@gmail.com wrote:
In a close race, I don't think we should get bogged down in
micro-optimization here, both because micro-optimizations may not gain
much and because what works well on one platform may not do much at
all on another. The more general issue
On Wed, Dec 1, 2010 at 12:30, Hitoshi Harada umi.tan...@gmail.com wrote:
From a user's view, this is very long way to see a simplest foreign
table. I know it is based on the standard, but I really want a
shortcut. Especially, I don't understand why CREATE USER MAPPING FOR
current_user SERVER
On tis, 2010-11-30 at 15:49 -0500, Tom Lane wrote:
Peter Eisentraut pete...@gmx.net writes:
On mån, 2010-11-29 at 13:10 -0500, Tom Lane wrote:
Rolling in calloc in place of
malloc/memset made no particular difference either, which says that
Fedora 13's glibc does not have any optimization
2010/12/1 Itagaki Takahiro itagaki.takah...@gmail.com:
On Wed, Dec 1, 2010 at 12:30, Hitoshi Harada umi.tan...@gmail.com wrote:
From a user's view, this is very long way to see a simplest foreign
table. I know it is based on the standard, but I really want a
shortcut. Especially, I don't
Josh Berkus j...@agliodbs.com writes:
On 11/30/10 7:09 PM, Tom Lane wrote:
Josh Berkus j...@agliodbs.com writes:
Apparently, testing for O_DIRECT at compile time isn't adequate. Ideas?
We should wait for the outcome of the discussion about whether to change
the default wal_sync_method
On Wed, 1 Dec 2010 12:30:46 +0900
Hitoshi Harada umi.tan...@gmail.com wrote:
This is another topic, but it would be useful if CREATE FOREIGN TABLE
can omit column definitions since fdw usually knows what should be
there in the definitions. I some times mistyped the column names
between remote
So I just made a commit that touched four files in all six active
branches, and I see:
$ git push
Counting objects: 172, done.
Compressing objects: 100% (89/89), done.
Writing objects: 100% (89/89), 17.07 KiB, done.
Total 89 (delta 80), reused 0 (delta 0)
To
Hello,
Maybe you are interested about this what I done with JDBC
=== Original driver (Text mode) ===
* Memory *
1. Memory usage improvments when using result set input streams (no uneeded
memory copy) - needs few touches for bigger performance.
2. Memory usage improvments for large data, should
On Wed, Dec 01, 2010 at 01:03:26AM -0500, Tom Lane wrote:
So I just made a commit that touched four files in all six active
branches, and I see:
$ git push
Counting objects: 172, done.
Compressing objects: 100% (89/89), done.
Writing objects: 100% (89/89), 17.07 KiB, done.
Total 89
On 01.12.2010 03:35, Bruce Momjian wrote:
Heikki Linnakangas wrote:
Let's recap what happens when a VM bit is set: You set the
PD_ALL_VISIBLE flag on the heap page (assuming it's not set already, it
usually isn't), and then set the bit in the VM while keeping the heap
page locked.
What if we
101 - 116 of 116 matches
Mail list logo
