Hello pgsql-general,
I'd like to set up a foreign key constraint to a foreign table from a local
table.
ie, I have a column in a local table that I'd like to ensure has a value in
the foreign table.
alter mytable
add column some_column_id uuid references myforeigntable(some_column_id)
;
On 22/06/15 19:00, Jeff Janes wrote:
A typical query on this table looks like this:
explain analyze
select log_date, host, msg
from logs_01 as log where log.msg like '%192.23.33.177%'
and log.log_date = '2015-1-18 1:45:24'
and log.log_date =
Albe Laurenz laurenz.a...@wien.gv.at writes:
Piotr Gackiewicz wrote:
Douglas Stetner stet...@icloud.com writes:
Looking for confirmation there is an issue with pg_dump failing after
upgrade to openssl-1.0.1e-30.el6_6.11.x86_64 on redhat linux.
I have the same problem with fresh postgresql
Thanks Will!
I had been considering setting up replication (using SymmetricDS - which we
already use between other databases in our environment), but decided for
this one check it was too much trouble. I may change my mind on that point
again after all if I end up with a lot of dependencies like
I wrote:
I'm going to file this as a bug with Red Hat. In the meantime it looks
like we can suggest ssl_renegotiation_limit = 0 as a temporary workaround.
Done at
https://bugzilla.redhat.com/show_bug.cgi?id=1234487
regards, tom lane
--
Sent via pgsql-general
Rick Otten rottenwindf...@gmail.com writes:
Hello pgsql-general,
I'd like to set up a foreign key constraint to a foreign table from a local
table.
ie, I have a column in a local table that I'd like to ensure has a value in
the foreign table.
alter mytable
add column some_column_id
Hello Rick,
As I understand it you are correct. Oracle/DB2/Postgres and I think the SQL
Standards to not implement constraints against tables on foreign servers.
Although it would be possible to develop the DBMS to handle such
constraints in a heterogeneous distributed environment it would be
On Mon, Jun 22, 2015 at 4:51 AM, Christian Ramseyer r...@networkz.ch wrote:
Hi
I have a pretty large table with syslog messages.
It is already partitioned by month, and for a single month I have e.g.
DM=# \d+ logs_01
Column|Type |
Obviously the server will be able to delete those rows because it will be
completely unaware of this dependency.
So it is the implied reverse constraint (of sorts) that can't be enforced
which makes an FK based definition impossible.
For my particular use case, this shouldn't be a problem. The
Hi All:
Does postgresql support schema analyze. I could not find analyze schema
anywhere. Can we create a function to run analyze and reindex on all
objects in the schema. Any suggestions or ideas.
Thanks,
-Suresh Raja
On Mon, Jun 22, 2015 at 10:39 AM, Christian Ramseyer r...@networkz.ch wrote:
On 22/06/15 19:00, Jeff Janes wrote:
A typical query on this table looks like this:
explain analyze
select log_date, host, msg
from logs_01 as log where log.msg like '%192.23.33.177%'
Hi
I have a pretty large table with syslog messages.
It is already partitioned by month, and for a single month I have e.g.
DM=# \d+ logs_01
Column|Type |
--+-+
host |
Piotr Gackiewicz wrote:
Tom Lane t...@sss.pgh.pa.us wrote:
Douglas Stetner stet...@icloud.com writes:
Looking for confirmation there is an issue with pg_dump failing after
upgrade to openssl-1.0.1e-30.el6_6.11.x86_64 on redhat linux.
Quick thought --- did you restart the Postgres service
Paula Price wrote:
I have Postgresql 9.2.10 streaming replication set up with log shipping in
case the replication falls behind. I discovered that the log-shipping had
been disabled at some point in time. I enabled the log shipping again.
If at some point in time the streaming replication
Adrian Klaver wrote:
On 06/20/2015 12:41 PM, Charles Clavadetscher wrote:
I just made a short test with the code provided. As Bill mentioned the
moment when the trigger is fired is essential.
I made a test with both before (worked) and after (did not work because
the row was already inserted
I wrote:
I'm going to file this as a bug with Red Hat. In the meantime it looks
like we can suggest ssl_renegotiation_limit = 0 as a temporary workaround.
Done at
https://bugzilla.redhat.com/show_bug.cgi?id=1234487
BTW, we should not feel too awful, because it seems this same update has
Hey all,
I have an odd performance quirk I wonder if anyone has any theories for… (not a
one-time result, table all heated up, etc)
spain=# explain analyze select way from planet_osm_point;
QUERY PLAN
Paul Ramsey pram...@cleverelephant.ca writes:
I have an odd performance quirk I wonder if anyone has any theories forâ¦
(not a one-time result, table all heated up, etc)
spain=# explain analyze select way from planet_osm_point; Â Â Â Â Â Â Â
             Â
18 matches
Mail list logo
