Thanks for looking into this! I tried your workaround on both 9.3.6 and
9.4.1 on Windows (64-bit), but it made no difference for me. If I put
the SET TRANSACTION statement before BEGIN on 9.4.1 I get WARNING: SET
TRANSACTION can only be used in transaction blocks - but putting it
inside the
Hi,
I noticed an inaccuracy in the transaction isolation docs. Under the
Repeatable Read Isolation Level section it states:
“The Repeatable Read isolation level only sees data committed before the
transaction began; it never sees either uncommitted data or changes committed
during
Sorry, I was trying to ask something very abstract as I have similar situations
on multiple groups of queries/tables (and they're all much more complex).
I'm on pg 9.3
The relevant structure is:
posting:
id
timestamp_publish
group_id__in
user_id__author
Since you very nicely DID NOT provide the pg version, O/S or table
structure(s), which is what you should do REGARDLESS of the
type of question (it's just the smart and polite thing to do when asking
for help) The best I can suggest is:
SELECT
CASE WHEN context = 'friend' THEN p.junka
On 4/27/15 7:54 PM, Craig Ringer wrote:
If 'default replication set' is the idea of here's what tables
*should* be getting replicated regardless of whether that's
happening or not, it'd be great if that was done so it could be
split out on it's own at some point. It's a problem
On 4/28/15 6:57 PM, Jonathan Vanasco wrote:
The relevant structure is:
posting:
id
timestamp_publish
group_id__in
user_id__author
friends:
user_id__a
user_id__b
memberships:
user_id
group_id
role_id
On Mon, Apr 27, 2015 at 7:45 AM, Evan Martin postgre...@realityexists.net
wrote:
I submitted the following bug report through the web form a few days ago.
It's causing problems in my application and I've been unable to find a way
to get around it. If someone here, familiar with PostgreSQL
Greetings,
I'm in the process of upgrading PG 9.1.3 to 9.4.1 in the near future.
I have several machines which each house unique databases. Each of those are
replicated to a standby server with matching configurations. A total of 10
servers, 5 masters, 5 slaves. Everything runs on Ubuntu.
Hi,
I am new to postgreSQL and facing an issue with the transactions which are
being shown in pg_locks.
We are using a script which deletes entries from a table called
audottrailLogEntry table.
This script first does the indexing then it deletes the entries from the table.
Now issue is that
On Tue, Apr 28, 2015 at 08:00:24PM +, Nicholson, Brad (Toronto, ON, CA)
wrote:
Hi,
I noticed an inaccuracy in the transaction isolation docs. Under the
Repeatable Read Isolation Level section it states:
“The Repeatable Read isolation level only sees data committed before the
I'm trying to upgrade some code that powers a newfeed type stream, and hoping
someone can offer some insight on better ways to structure some parts of the
query
The part that has me stumped right now...
There are several criteria for why something could appear in a stream. for
example, here
11 matches
Mail list logo
