On Thu, Jun 12, 2014 at 12:25 PM, Ian Barwick wrote:
> On 14/06/12 18:46, Jochem van Dieten wrote:
> > I haven't checked the code, but I am hoping it will help with the problem
> > where a RETURNING * is added to a statement that is not an insert or
> update
> > by t
d is neither very elegant nor very robust:
https://groups.google.com/forum/#!msg/pgsql.interfaces.jdbc/7WY60JX3qyo/-v1fqDqLQKwJ
Jochem
--
Jochem van Dieten
http://jochem.vandieten.net/
se SQLite for bookmark storage?) will weight far heavier then
some perceived enterprise readiness,
Jochem
--
Jochem van Dieten
http://jochem.vandieten.net/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Thu, Sep 11, 2008 at 2:07 AM, Simon Riggs wrote:
> Transaction snapshots is probably the most difficult problem for Hot
> Standby to resolve.
> * remotely from primary node
> * locally on the standby node
>
> If we derive a snapshot locally, then we will end up with a situation
> wher
On Thu, Aug 7, 2008 at 12:38 PM, Simon Riggs wrote:
> I propose creating "Visibility Groups" that *explicitly* limit the
> ability of a transaction to access data outside its visibility group(s).
Doesn't every transaction need to access data from the catalogs?
Wouldn't the inclusion of a catalogs
On Mon, Mar 17, 2008 at 6:23 PM, Tom Lane wrote:
> Simon Riggs writes:
>>
>> Can we call them "maps" or "metadata maps"? "forks" sounds weird.
>
> I'm not wedded to "forks", that's just the name that was used in the
> only previous example I've seen. Classic Mac had a "resource fork"
> and a "d
On Thu, Feb 28, 2008 at 1:19 AM, Tom Lane wrote:
> I think the question we have to answer is whether we want to be
> complicit in the spreading of a nonstandard UUID format.
I don't.
I have patched the UUID input and output functions to be compatible
with Adobe ColdFusion (http://adobe.com/prod
On Mon, Feb 11, 2008 at 5:51 PM, Tom Lane wrote:
> I agree. Since any multiple-output-file case can't usefully use stdout,
> I think we should combine the switches and just have one switch that
> says both that you want separated output and what the target filename
> is. Thus something like
>
On 2/1/07, Chris Dunlop wrote:
In maillist.postgres.dev, you wrote:
On Thu, 1 Feb 2007, Chris Dunlop wrote:
The main idea is that, there might be space utilisation and
performance advantages if postgres had "hard" read-only
tables, i.e. tables which were guaranteed (by postgres) to
never have
On 12/29/06, Stephen Frost wrote:
So, Debian is distributing an application (exim4 w/ libpq & libssl)
which includes GPL code (exim4) combined with code under another license
(BSD w/ advertising clause) which *adds additional restrictions* (the
advertising clause) over those in the GPL, which is
On 12/28/06, ITAGAKI Takahiro wrote:
| [TODO item] Allow data to be pulled directly from indexes
| Another idea is to maintain a bitmap of heap pages where all rows are
| visible to all backends, and allow index lookups to reference that bitmap
| to avoid heap lookups
It is not done yet, but we
On 7/6/06, [EMAIL PROTECTED] wrote:
Please answer the below questions, and state whether your opinion is
just an opinion, or whether you are stating it as a PostgreSQL
maintainer and it is law. If you wish, you can rank preferences.
1) The added 128-bit type should take the form of:
a) UUI
On 6/24/06, Mark Woodward wrote:
ver001->verN->...->ver003->ver002->|
^-/
This will speed up almost *all* queries when there are more than two
version of rows.
OK, here is the behavior of an update:
(1) Find the latest version of the row
(2) Duplicate row and m
On 6/23/06, Mark Woodward wrote:
For each update to a row additional work needs to be done to access that
row. Surely a better strategy can be done, especially considering that the
problem being solved is a brief one.
The only reason why you need previous versions of a row is for
transactions t
On 6/22/06, Mark Woodward wrote:
(..)
thousand active sessions
(..)
If an active user causes a session update once a second
(..)
Generally speaking, sessions aren't updated when they change, they are
usually updated per HTTP request. The data in a session may not change,
but the session hand
On 2/11/06, Andrej Ricnik-Bay wrote:
> Has anyone here seen this one before? Do the values
> appear realistic?
>
> http://www.sqlite.org/cvstrac/wiki?p=SpeedComparison
The values appear to originate from an intrsinsically flawed test setup.
Just take the first test. The database has to do 1000 co
On 12/6/05, Hannu Krosing wrote:
>
> 1) run a transaction repeatedly, trying to hit a point of no concurrent
> transactions, encance the odds by locking out starting other
> transactions for a few (tenths or hundredths of) seconds, if it
> succeeds, record SNAP1, commit and and continue, else rollb
On 12/5/05, Hannu Krosing wrote:
>
> Concurrent CREATE INDEX
>
>
> Concurrent index NDX1 on table TAB1 is created like this:
>
> 1) start transaction. take a snapshot SNAP1
>
> 1.1) optionally, remove pages for TAB1 from FSM to force (?) all newer
> inserts/updates to happe
On 12/3/05, Tom Lane wrote:
> Jochem van Dieten writes:
>> How about the following sceanrio for building a new index:
>> - create an empty index
>> - flag it as incomplete
>> - commit it so it becomes visible to new transactions
>> - new transactions will update th
On 12/2/05, Alvaro Herrera wrote:
> Gregory Maxwell wrote:
>>
>> After you're mostly caught up, change locking behavior to block
>> further updates while the final catchup happens. This could be driven
>> by a hurestic that says make up to N attempts to catch up without
>> blocking, after that just
On 11/13/05, Petr Jelinek wrote:
>
> I am really not db expert and I don't have copy of sql standard but you
> don't need to use 2 tables I think - USING part can also be subquery
> (some SELECT) and if I am right then you could simulate what REPLACE
> does because in PostgreSQL you are not forced
On 11/4/05, Jim C. Nasby wrote:
>
> I would argue that in cases like this (and 'this' means just about any
> DDL, for starters) that it would be better not to block everyone until
> work can actually be done. Or at least make that an option.
Would it be possible to simulate this by manually trying
On 9/26/05, Dennis Bjorklund wrote:
> On Sun, 25 Sep 2005, Tom Lane wrote:
>>
>> Alternatively: why are we forbidding the value 24:00:00 anyway? Is
>> there a reason not to allow the hours field to exceed 23?
>
> One reason is because it's what the standard demand.
Could you cite that? The only th
On 9/11/05, Bruno Wolff III wrote:
> On Sat, Sep 10, 2005 at 14:31:06 -0400, Andrew Dunstan wrote:
>>
>> XHTML is simply a minimal reformulation of HTML in XML, and even uses
>> the HTML 4.01 definitions for its semantics. Given that, it's hard to
>> see why it should be considered a bad thing.
>
On 29 Aug 2005 09:56:44 +0200, Harald Fuchs wrote:
> Christopher Kings-Lynne writes:
>>
>> Oh, and 'select rowid, * from table' which returns special rowid
>> column that just incrementally numbers each row.
I think you can pretty much do that already by defining your own
aggregate function. The o
On 7/26/05, Jim C. Nasby wrote:
> On Tue, Jul 26, 2005 at 01:09:11PM -0700, Jeff Davis wrote:
>>
>> Ultimately to do it in a general way I think we'd need functions that
>> return a type that can be used in a table definition. Aside from the
>> many problems I don't know about, there are two other
On 7/14/05, Michael Paesold wrote:
> Christopher Kings-Lynne wrote:
>>
>> usatest=# explain select * from users_myfoods_map where date='2004-11-21'
>> order by date;
>> QUERY PLAN
>> ---
>> Sort
I can't believe I am the first one to respond to this :)
On 6/27/05, Simon Riggs wrote:
> On Mon, 2005-06-27 at 01:41 +0100, Simon Riggs wrote:
>>
>> The main purpose of this feature is to reduce access time against large
>> tables that have been split into partitions by using the PostgreSQL
>> in
On 6/11/05, Heikki Linnakangas wrote:
>
> It matches with the format in the JTA spec, but the JTA spec also mentions
> the OCI CCR format
The "OSI" CCR format, which appears to refer to ISO/IEC 9805-1.
ISO/IEC 9805-1:1998
15-12-1998
Information technology - Open Systems Interconnection - Protoc
On 6/1/05, Bruce Momjian wrote:
> Jochem van Dieten wrote:
>>
>> Why only on an empty table? What is the problem with bypassing WAL on
>> any table as long as all files of that table are fsync'ed before
>> commit?
>
> Because adding rows to a table might mo
On 01 Jun 2005 04:44:24 -0400, Greg Stark wrote:
> Greg Stark writes:
>>
>> For CREATE TABLE AS in the non-PITR case you don't really need to WAL log the
>> records at all. If it fails in the middle you just drop the table. When it
>> completes you do a checkpoint before acknowledging the COMMIT.
On 5/28/05, Tom Lane wrote:
>
> I think they may have intended to treat each time interval
> as the half-open interval [S,T), that is S <= time < T. However
> that would leave a zero-length interval as completely empty and
> thereby arguably not overlapping anything ... which they didn't
> make i
On 5/27/05, Mario Weilguni wrote:
> I've quite some trouble with the overlaps function:
> SELECT overlaps('9.6.2005'::date, '9.6.2005'::date, '9.6.2005'::date,
> '9.6.2005'::date);
> returns true (these are german timestamps dd.mm.)
>
> SELECT overlaps('8.6.2005'::date, '9.6.2005'::date, '9.6.
On 5/7/05, Alvaro Herrera wrote:
> On Fri, May 06, 2005 at 03:30:10PM -0700, Joshua D. Drake wrote:
>>
>> Rendezvous is the Apple network discovery protocol yes? That was renamed
>> Bonjour by apple due to a Trademark problem.
>
> Maybe we should name it Zeroconf.
Is the implemented protocol IE
On 5/2/05, Jim C. Nasby wrote:
> Out of curiosity, what would be required to allow deletes (but not
> updates)?
The same as updates (because updates are essentially a delete + insert).
> My thinking is that you'd want *some* way to be able to prune
> data. Since you won't want to store an entire
On 4/24/05, Tom Lane wrote:
>
> What you are talking about is not a "read only" table, it is a
> "non-MVCC" table. This is a much greater assault on the fundamental
> semantics of Postgres than it's being painted to be in this thread.
> In particular, how is such a table going to come into being?
On 4/22/05, Hannu Krosing wrote:
> Fetching data from just indexes has been discussed on this list several
> times before, and it has been told that this can't be done with postgres
> thanks to MVCC.
>
> But this is true only when data is changing. In a data-warehousing
> scenario what it is often
On Sun, 16 Jan 2005 20:01:36 -0500, Tom Lane wrote:
> "Jim C. Nasby" writes:
>> Wouldn't the original proposal that had a state machine handle this?
>> IIRC the original idea was:
>>
>> new tuple -> known good -> possibly dead -> known dead
>
> Only if you disallow the transition from possibly de
On Sun, 16 Jan 2005 20:49:45 +0100, Manfred Koizar wrote:
> On Thu, 13 Jan 2005 00:39:56 -0500, Tom Lane wrote:
>> A would-be deleter of a tuple would have to go and clear the "known
>> good" bits on all the tuple's index entries before it could commit.
>> This would bring the tuple back into the "
On Tue, 26 Oct 2004 18:12:36 +0200, Jos van Roosmalen wrote:
>
> I have a little question. Why performs Postgresql a Seq. Scan in the
> next Select statement instead of a Index Read?
That is a FAQ: http://www.postgresql.org/docs/faqs/FAQ.html#4.8
Please direct any further questions of this natu
On Fri, 02 Jul 2004 14:57:18 +0300, Hannu Krosing <[EMAIL PROTECTED]> wrote:
>
> IIRC we were recently told (in this thread) that the SQL standard tells
> to end local customisations with underscore, so it would be
> 'column_comment_'
I didn't write that (or at least, I didn't mean to write that
On Thu, 1 Jul 2004 12:23:10 -0500, Bruno Wolff III <[EMAIL PROTECTED]> wrote:
>
> Is there any provision in the information schema part of the standard for
> vendor specific extensions?
Yes, there is:
"An SQL-implementation may define objects that are associated with
INFORMATION_SCHEMA
Jonathan Gardner wrote:
Seeing how PITR, nested transactions, and other exciting developments
related to transactions are being developed, I am getting curious about how
PostgreSQL actually implements transactions. Investigating Materialized
Views has led me to look closely at how transactions w
[EMAIL PROTECTED] wrote:
(5) Programming languages. We need to make a programming language standard
in PostgreSQL. plpgsql is good, but isn't someone working on a Java
language. That would be pretty slick.
IMHO SQL/PSM would be the obvious choice for the standard
procedural language. Not only beca
Tom Lane wrote:
It's the oldest xmin of any transaction that's local to your database,
but those xmin values themselves were computed globally --- so what
matters is the oldest transaction that was running when any local
transaction started. In this case I expect it's the VACUUM's own
transaction
Jan Wieck said:
>
> The communication channels are "event" tables. The node daemons
> use listen and notify to send messages from on to another.
> Messages are only exchanged over this when the replication cluster
> configuration is changed or every 10 seconds to tell "new
> replication data has
Josh Berkus wrote:
I personally don't think that a GUI tool should be the province of the Slony
project. Seriously. I think that Slony should focus on a command-line api
and catalogs, and allow the existing GUI projects to build a slony-supporting
interface.
Why a command line api? I believe
ivan wrote:
pg_dump: handler procedure for procedural language "plpgsql" not found
pg_dumpall: pg_dump failed on database "db", exiting
why ?
Perhaps the pg_dump bug with procedural language handlers which
have been created in the pg_catalog schema:
http://archives.postgresql.org/pgsql-general/200
Jan Wieck wrote:
As a PostgreSQL coreteam member I want to thank my employer, the
PeerDirect Corporation, for contributing this work, which IMHO is an
important step for PostgreSQL.
Yes, a very important step. A big thank you to PeerDirect.
What we need from here are some ideas how this port
49 matches
Mail list logo
