hrase
such as "custom prompt" in the mailing list archives? Everything I tried found
every page with either the word custom, the word prompt, or both words
somewhere in the message. I just wanted to search for messages containing the
exact phrase "custom prompt".
Thanks,
Cra
>> When accessing PostgreSQL via psql, is it possible to make use of a custom
>> prompt? I would like something like postgres=# instead of just postgres=#. My
>> search was fruitless (see next paragraph).
>
> Should have added:
> To make it stick between sessions you can use a psqlrc file. They ar
>
> Try along the lines of
>
> psql -h some.host.com -U postgres -v "PROMPT1=*my_cool_prompt%/> " -d my_db
>
Works like a charm! Do I have a dot file that I can save this setting to,
similar to the .exrc for vi, or will I need to enter it every time? If the
latter, I'll alias it, but I'd
Apologies to all, I didn't realize this ISPs webmail client doesn't wrap lines.
My reply, formatted in a more readable way:
On Monday, September 24, 2012 14:07, cr...@gtek.biz said:
>> When accessing PostgreSQL via psql, is it possible to make use of a custom
>> prompt? I would like something lik
> Aha, exactly what I was looking for. Thanks!
Well I certainly feel dumb. The answer is right in the documentation, I just
failed to find it (I did look first). The system-wide psqlrc, and the ~/.psqlrc
files fit the bill perfectly, and the documentation explains it all quite
nicely. I accom
he desired search results?
Enclosing a phrase in quotes works with most mailing list archives, with most
search engines, and in queries. So surely there is a way to perform a similar
search on the PostgreSQL archives?
Thanks,
Craig
Sent - Gtek Web Mail
--
Sent via pgsql-general mailing l
>
> On 10/31/2012 12:59 PM, cr...@gtek.biz wrote:
>> list all role privileges
>
> Google:
>
> site:archives.postgresql.org 'list all role privileges'
>
> --
I was kind of hoping "The world's most advanced open source database." would
offer this functionality without having to rely on an outsi
an ORDER BY clause
A Simplistic example:
SELECT f1, f2, f3, sum(f4)
FROM TableA
GROUP BY f1, f2, f3
ORDER BY f2,f1,f3
Now I would like to add another field that simply
return 1,2,3,4,5,etc.. for each row that is returned.
Can this be done?
Thanks
Craig
Hi
What is the best tool for debugging pl/pgsql
functions?
Any suggestions would be appreciated
Thanks
Craig
min is not present.
This moduel gets installed in the Windows
installation automatically (admin.dll in the lib folder).
Can anyone help?
Thanks
Craig
on a
64-bit OS, or should I run the 32 bit OS for now?
Any help will be greatly appreciated
Thanks
Craig
Hi
How can I query for all the tables that are
referenced by a particular table (i.e my table has 3 foreign keys. I need a
query that will return the table names of the referenced tables)?
Thanks
Craig
help will be greatly appreciated
Craig
support to the running version of postgres. This is a production server and
I cannot really afford any down time.
I installed PostgreSQL 8.1.0 from source.
Any help will be much appreciated
Thanks
Craig
Hi Andreas
I explained the situation badly. I had "originally" installed from source
WITHOUT perl support. I would now like to add it, please can you explain how
I would do that without completely re-installing PostgreSQL?
I had already tried the creatlang command
Th
Hi,
I am looking for an RPM to install the ODBC driver for PostgreSQL 9.0.2. The
repository contains quite a few RPMs but only the source code for the ODBC
driver. Is there another place I can look for an RPM for this?
Thanks,
Craig
No I didn't. That looks like what I'm looking for. Thanks!
Craig
-Original Message-
From: Devrim GÜNDÜZ [mailto:dev...@gunduz.org]
Sent: Tuesday, March 29, 2011 9:32 PM
To: Worgan, Craig (Craig)
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] RPM for ODBC driver
On
catalog_xmin
> value. Should I expect the 'xmin' value to be null? Is there another way
> to monitor the replication latency when using BDR?
>
> Thanks,
> Steve Boyle
>
>
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
d on one node, I
> would expect the 'xmin' value not to be null but is.
>
> What is the best way to monitor replication latency when using Postgresql
> BDR?
>
> Regards,
>
> Bill
>
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
with an error.
If your apps aren't written that way then you clearly don't mind showing
errors to the user that much after all.
> Is there a mechanism a new node gets added on the fly ?
>
It's been added in the coming 0.9.0 release.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
in the pending 0.9.0 release. However,
all nodes are expected to be up and reachable when you add a new node. Node
addition won't complete until they are. Allowing node addition while one or
more peers are down is not on the current roadmap. If you have a dead node
you must remove it before add
e?
At this time I think you'd have to patch the BDR apply worker to do what
you wanted.
There are already a few areas where downstream filtering or apply hooks are
of interest, so this might be an area that can be enhanced in future.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
how and
when they upgrade. See http://yum.baseurl.org/wiki/Faq for more on version
pinning.
The release announcement for BDR 0.9.0 will have a lot more detail.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
ey are run in.
Thanks for writing a clear and detailed report with errors, versions, and
command shown. It's much appreciated.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
On 25 March 2015 at 20:14, Peter Mogensen wrote:
>
>
> On 2015-03-25 12:32, Craig Ringer wrote:
>
>> On 25 March 2015 at 19:15, Peter Mogensen wrote:
>>
>> Say ... I have a table in a BDR replicated database with an "ON UPDATE"
>>> trigger.
eam commit's
LSN at the C level from the BDR apply worker during transaction replay,
though. The LSN provides strict ordering for a node.
I'd start by looking into whether commit timestamps can meet your needs.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
(Please reply-to-all to keep the thread on pgsql-general)
On 26 March 2015 at 18:32, Peter Mogensen wrote:
>
>
> On 2015-03-26 10:14, Craig Ringer wrote:
>
>> I see what you're getting at. You want to prevent stale data from being
>> reinsterted into a cache b
On 26 March 2015 at 19:08, Peter Mogensen wrote:
>
>
> On 2015-03-26 11:57, Craig Ringer wrote:
>
>> If that's the case then BDR shouldn't make any difference.
>>
>
> It does. Because now with BDR you can't compare txid_current() as saved on
> the
I'll make the docs more explicit about that.
> I need to be able run a query on node ‘B’ to determine if it node ‘B’ is
> behind. I am not sure the above query will work for that use case.
It won't, and you really can't.
--
Craig Ringer http://www.
ted.
>
Just make direct libpq connections to each node from the monitoring host.
You should generally be doing that anyway for your node health monitoring.
If you can't make inbound connections, do it on a push model, e.g. nsca-ng
and Icinga's passive mode. This is something that'
ion sets
before starting to add data to tables.
All this applies to 0.9.0 and is, of course, subject to change in future
releases, time and resources permitting.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
set, table sync when replication sets
are changed, etc.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
On 28 April 2015 at 05:38, Jim Nasby wrote:
> On 4/26/15 7:49 AM, Craig Ringer wrote:
>
>> There are also some improvements needed to the user interface - in
>> particular, providing a function interface for changing replication set
>> memberships for connections so the
On 29 April 2015 at 09:14, Jim Nasby wrote:
> 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
BDR is the perfect solution for our
> infrastructure's needs for backup and availability
>
You might want to consider BDR's single-master UDR mode too, or tools like
Londiste. Don't add multi-master unless you really need it. Significant
limitations are introduced around how and when you can do DDL, etc, when
doing multi-master BDR, per the manual.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
t. It's certainly not going to when
comparing between nodes, especially in an async system.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
to either support parallel join of multiple
nodes or identify and reject it.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
On 12 May 2015 at 14:36, Wayne E. Seguin wrote:
> Also,
>
> Is there a way to remove these things from the init target node easier?
>
> d= p=504 a=ERROR: 55000: previous init failed, manual cleanup is required
> d= p=504 a=DETAIL: Found bdr.bdr_nodes entry for bdr
> (6147869128174526660,1,16908
On 12 May 2015 at 22:21, Wayne E. Seguin wrote:
> Craig,
>
> It's alive!!!
>
> One more question on this thread, where can I find the meanings of
> node_status in the documentation?
>
node_status is really internal, but it's covered briefly in the docs:
htt
On 13 May 2015 at 09:29, Wayne E. Seguin wrote:
> *awesome*, the question was for my own curiosity so thanks for this!
>
No worries.
I know it's trite, but for internal-ish detail like that the best reference
remains the source code. I'd like to think the sources are fairly sa
On 15 May 2015 at 04:26, Dennis wrote:
>
> What am I missing? How are the steps different from setting database
> replication?
>
>
Please show the log output from both nodes, and the contents of "SELECT *
FROM bdr.bdr_nodes" and "SELECT * FROM bdr.bdr_connectio
or this use case too. If you
don't need multi-master, don't use multi-master.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
derstand.
If you mean join and remove nodes, join with bdr.bdr_group_join, remove
with bdr.bdr_part_by_node_names .
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
the command filter off.
BEGIN;
SET LOCAL bdr.permit_unsafe_ddl_commands = true;
SET LOCAL bdr.skip_ddl_locking = true;
security label for 'bdr' on database bdr_testdb is '{"bdr": false}';
COMMIT;
Out of interest, why do you want to detach a node and keep using it as
a st
king control of the application.
Absolutely. The trouble is that all such things have trade-offs.
For example, with the ability to re-attach a node that you asked
about, doing so can't be done without accumulating lots of upstream
WAL. It'd be effectively identical to just shutting
iscussion in one
place.
https://github.com/2ndQuadrant/bdr/issues/88
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscri
ime and hassle.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
des and bdr.bdr_connections, and remove the bdr security
label with:
SECURITY LABEL FOR bdr ON DATABASE thedb IS NULL;
then restart the DB. You may also wish to remove 'bdr' from
'shared_preload_libraries'.
--
Craig Ringer http://www.2ndQuadr
it?
2ndQuadrant maintains repmgr. I think it's a decent tool for the job.
> Is it a good tool
> or is there something better for the same use case that repmgr fulfills.
It's moderately easy to just do it by hand if you don't want to use
repmgr. I haven't look
oss-node
querying. So in practice it's no benefit over a bunch of standalone
databases.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To mak
me what would be the best approch for this.
>From your description it sounds like BDR is not particularly suitable
for your use case at this time.
We're looking at adding sharding down the track, but it's quite a way
down the track because there's a fair bit of work on makin
e optimisation. I can't know without a lot more info.
Rather than starting with the solution (horizontal partitioning,
sharding) try starting with the problem and requirements, then looking
for solutions from there.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Deve
ple
single-master replication will do just as well.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http
een removed.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
r_node_join wait until the join completes, because it's
necessary to co-ordinate with background workers, commit multiple
transactions, etc.
It's not clear from your description what you mean by "on an existing
database". Details?
--
Craig Ringer http
On 2 September 2015 at 00:12, cchee-ob wrote:
> Craig,
>
> By an existing database, I mean I have a database that has our data on it.
> I have created the btree_gist and bdr extensions and ran the
> bdr.bdr_group_create () function and the bdr.bdr_node_join_wait_for_rea
ot use FDWs in a BDR-enabled database.
> (maybe one could create the FDW before configuring replication)
No.
It's possible to override the filter using documented settings, but I
don't advise doing so unless you're extremely sure you need this, and
understand exactly
On 2 September 2015 at 20:40, Andres Freund wrote:
> On 2015-09-02 20:27:40 +0800, Craig Ringer wrote:
>> The reason for this is that BDR replicates at a database level, but
>> CREATE SERVER and CREATE USER MAPPING are global, affecting all
>> databases on a PostgreS
; PATH=/path/to/install:"$PATH" ./configure
> make -j4 -s all
Thanks, now fixed in the devel tree.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-general mailing list (pg
ling list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
CE and use it as the default RADIUS identifier, but I
fail to see how those could get passed as the login role identifier.
Are you running it under a unix user named "postgresql", by any chance?
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Developmen
er).
Correct.
> Is there any workaround?
Keep it simple. Use streaming replication and a hot standby.
> For "traditional" (non BDR) serial, there is a way to set into configuration
> what will be START and INCREMENT of all sequences?
No.
> Or each serial sequence must be
tition tolerance is needed, yes, it could make a lot of sense.
You could use UUID keys or use normal sequences with different offsets
on the nodes. UUID will probably be easier to manage.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Tr
On 7 September 2015 at 20:34, Ray Stell wrote:
>
>
> On 9/6/15 10:55 PM, Craig Ringer wrote:
>>
>> On 4 September 2015 at 21:46, Ray Stell wrote:
>>>>>>
>>>>>> FATAL: role "postgresql" does not exist
>>>>>
>
> $ git rev-parse --short HEAD
> 6a60690
>
> $ git branch
> * bdr-pg/REL9_4_STABLE
OK, that's PostgreSQL. What about the BDR extension its self?
SELECT bdr.bdr_version() will show you if you're starting up OK,
otherwise again the git rev please.
--
Craig Ringer
inly on RHEL/CentOS/Fedora, but Debian/Ubuntu
packages are also produced. We're a little behind at the moment and
haven't got 0.9.2 packages out. I'll be pushing 0.9.3 soon and will
produce 0.9.3 packages for Debian/Ubuntu as well as for
Fedora/RHEL/CentOS.
--
Craig Ringer
>>
>>> Is it a feature or a bug?
>>
>> I think it's an oversight. Replication sets were added later than the
>> TRUNCATE trigger, so the design for the latter does not consider the
>> former as far as I know.
>
> Ok. May I fill a bug report?
> Basically, how do I reset BDR completely? It seems to retain the memory of
> the bdrdemo database somewhere.
Sort-of. What happens in your example is that when you part the nodes,
they're separated and stop communicating. So your second part command
never reaches the remaining node.
connections entries and those
associated with terminated nodes are ignored.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscr
1_1_48609__ | bdr| logical | 19685 |
> deliver | t | | 2280 | 0/28EA5E0
>
> How can I get rid of the stale node recovery on startup?
Can you show the output of
select * from pg_replication_identifiers;
please? On all nodes. Also pg_catalog.pg_replication
BDR is currently memory-limited for extremely large transactions. At a
guess, I'd say one of your big tables is large enough that the logical
decoding facility BDR uses can't keep track of the transaction
properly.
There's no hard limit, it depends on details of the transaction and a
number of oth
b.com/2ndQuadrant/bdr/issues/133
The identifiers aren't currently dropped during node part, which
should be changed. It hasn't come up to date because frequent node
addition and removal is something to be avoided, and because most
deployments configure room for more slots than needed to
What's the *exact* BDR version?
When you say you "attempted to" - what was the outcome? Presumably an
ERROR from the TRUNCATE, right? That would roll back the transaction,
and in the process abort the DDL lock acquisition attempt.
Are you sure replication was working normally prior to this point,
just isn't sufficient to handle FK relationships,
and that the current test suite doesn't cover this.
I'm going to write a test to confirm what I think is going on, then follow up.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Suppor
7163,): perdb"
This is a bug fixed in 0.9.3.
https://github.com/2ndQuadrant/bdr/issues/126
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To
.2.0
Please update to 0.9.3, which fixes this issue, per
https://github.com/2ndQuadrant/bdr/issues/126
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.or
he sort of thing we can move toward with built-in
logical replication in coming releases.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
further than that and say I can't see how something like this could
possibly work with physical (block based) replication. It's total
hand-waving.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
s, but seem
to be ignoring that because it's not the solution you have already decided
you need for your problem.
I doubt anybody will implement this for you, especially since I don't think
it's really possible in PostgreSQL's block-based physical replication
architecture. So sa
t.
>
I think they're specifically referring to 2ndQ's BDR project here, rather
than bi-directional logical replication general.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
t multimaster or DDL replication
like BDR does, though.
You can also look into Londiste and Slony-I.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
Hello All,
I am something of a newbie and I am trying to understand how to pass
connection options using the psql client. My understanding is that it
is possible to do this as part of the psql connection event.
I am on Mint and my PostgreSQL Server version = 9.3.13.
I am trying to connect to
On 07/03/2016 06:15 PM, Melvin Davidson wrote:
On Sun, Jul 3, 2016 at 6:54 PM, Craig Boyd <mailto:cr...@mysoftforge.com>> wrote:
Hello All,
I am something of a newbie and I am trying to understand how to
pass connection options using the psql client. My understandi
On 07/03/2016 06:51 PM, Scott Marlowe wrote:
On Sun, Jul 3, 2016 at 5:15 PM, Melvin Davidson <mailto:melvin6...@gmail.com>> wrote:
On Sun, Jul 3, 2016 at 6:54 PM, Craig Boyd mailto:cr...@mysoftforge.com>> wrote:
Hello All,
I am something of a newbie and
wn
failures to connect using options on this page then I have to assume
that these are options that can be changed post login.
Thanks for everyone's help. This makes a bit more sense. :)
Sincerely,
Craig
On 07/04/2016 11:01 AM, Daniel Verite wrote:
Craig Boyd wrote:
So to put it another way: is there a list that shows what options are
available during the connection event or as part of the connection string?
Yes, but it belongs to the chapter on libpq. The psql docpage merely points
creation/drop, user creation/drop, etc, then it might make sense to extend
BDR or its successor to do this. But not at the moment.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
the tables can be in the millions.
Thanks,
Craig
MATCH SIMPLE
ON UPDATE NO ACTION ON DELETE NO ACTION,
CONSTRAINT unq_department_customerid_departmentname UNIQUE (customer_id,
department_name)
)
Thanks,
Craig
From: David G. Johnston [mailto:david.g.johns...@gmail.com]
Sent: Monday, August 8, 2016 11:33 AM
To: Craig Bou
my primary key
was (customer_id, work_session_id) or if (work_session_id, customer_id) will
be fine. Customer_id will be repeated quite a bit in the table but
work_session_id should be unique across the whole table.
Thanks,
Craig
From: David G. Johnston [mailto:david.g.johns
Thanks Tom for the link.
It could actually be beneficial if we need to migrate a customer from one
database to another because wouldn't have to worry about pk constraint
violations.
Craig
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Monday, August 8, 2016 1:
ng a department description as part of the
primary key in the department table and having it repeated in millions of rows.
Though I always look for ways to use natural keys where they work well.
Thanks,
Craig
-Original Message-
From: Kevin Grittner [mailto:kgri...@gmail.com]
Sent: Monday, Augu
NTO _words
> SELECT
> out_word AS word,
> max(out_score) AS score
> FROM check_words(in_uid, in_gid, in_tiles)
> GROUP BY word, gid;
>
>
Or use CREATE TABLE ... AS SELECT ...
That's the SQL-standard spelling any
other thing I can think of is a delete trigger on each of the
partition child tables. That would work, but it's a nuisance.
Thanks,
Craig
On Tue, Aug 23, 2016 at 1:07 PM, Igor Neyman wrote:
>
>
> *From:* pgsql-general-ow...@postgresql.org [mailto:pgsql-general-owner@
> postgresql.org] *On Behalf Of *Craig James
> *Sent:* Tuesday, August 23, 2016 4:00 PM
> *To:* pgsql-general@postgresql.org
> *Subject:*
bles it's necessary to block concurrent DML.
BTW, now that it's clear in-core logical replication is going in
another direction there's now a bdr-l...@2ndquadrant.com mailing list;
see https://groups.google.com/a/2ndquadrant.com/forum/#!forum/bdr-list
.
--
Craig Ringer
hanged() doesn't know to check for a
changed DSN. I'd welcome a patch to address that, since I probably
won't have time to get to it soon.
We should have a bdr.bdr_connection_set_dsn(...) function, really.
Again, a patch would be welcomed.
--
Craig Ringer
Increase wal_sender_timeout to resolve the issue.
I've been investigating just this issue recently. See
https://www.postgresql.org/message-id/camsr+ye2dsfhvr7iev1gspzihitwx-pmkd9qalegctya+sd...@mail.gmail.com
.
It would be very useful to me to know more about the transaction that
caused this prob
See also https://github.com/2ndQuadrant/bdr/issues/233
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
eing
updated at a time, will I reap the benefits?
Thanks,
Craig
1 - 100 of 1923 matches
Mail list logo
