Hi,
When I use "preparedStatement.setString(5,ip);" to send values to a
stored function, it obviously gets sent to postgres as "character
varying".
Postgres obviously complains loudly and says " Hint: No function
matches the given name and argument types. You might need to add
explicit type casts
On 2015-12-03 10:02:18 -0500, Tom Lane wrote:
> "Peter J. Holzer" writes:
> > Can those signals be safely ignored? Just blocking them (so that they
> > are delivered after the UDF finishes) might be safer. But even that may
> > be a problem: If the UDF then executes some SQL, could that rely on
>
On Fri, 2015-12-04 at 09:41 +, Tim Smith wrote:
> Hi,
>
> When I use "preparedStatement.setString(5,ip);" to send values to a
> stored function, it obviously gets sent to postgres as "character
> varying".
>
> Postgres obviously complains loudly and says " Hint: No function
> matches the give
On Fri, 4 Dec 2015 09:41:24 +
Tim Smith wrote:
> When I use "preparedStatement.setString(5,ip);" to send values to a
> stored function, it obviously gets sent to postgres as "character
> varying".
>
> Postgres obviously complains loudly and says " Hint: No function
> matches the given name a
On 12/2/15 6:25 PM, Jim Nasby wrote:
On 12/2/15 1:56 PM, David Steele wrote:
>Also, I don’t want enable archive_mode = on as it needs to maintain
>archives files.
As it turns out, archiving would be the solution to your problem. If
you were archiving you could restore a*previous* backup and t
On 12/3/15 12:59 AM, Yelai, Ramkumar IN BLR STS wrote:
What I wanted to achieve is simple copy of Data folder. I can't shutdown the
database during the backup and unable to use file system copy of data folder as
it creates inconsistency and don't want to use pg_dump.
Hence I decided to use Pg_
Hi @ll,
imagine a streaming replication using physical replication slots. And sometime a
fail over. All okay. I take a basebackup and rebuild the old master as slave.
Is there a risk that the new slave contains active replication slots but no
listener on it? What have i to consider?
Thx.
--
S
Someone has some way of identifying all invalid blocks of a table postgresql
?
Plpgsql a function, a tool, somehow.
I found one solution on
http://www.postgresql.org/message-id/1184245756.24101.178.ca...@coppola.muc.ecircle.de,
but I can not change in order to identify any defective blocks at onc
Someone has some way of identifying all invalid blocks of a table postgresql
?
Plpgsql a function, a tool, somehow.
I found one solution on
http://www.postgresql.org/message-id/1184245756.24101.178.ca...@coppola.muc.ecircle.de,
but I can not change in order to identify any defective blocks at onc
Yes they seem to be active:
deliver=# select * from pg_replication_slots;
slot_name | plugin | slot_type | datoid |
database | active | xmin | catalog_xmin | restart_lsn
--++---++--++-
> Selim Tuvi hat am 4. Dezember 2015 um 18:46 geschrieben:
>
>
> Yes they seem to be active:
>
> deliver=# select * from pg_replication_slots;
> slot_name | plugin | slot_type | datoid |
> database | active | xmin | catalog_xmin | restart_lsn
> ---
Le 04/12/2015 18:59, Andreas Kretschmer a écrit :
I think, the state 'i' is the main reason for your problem, because of: "i-
Joining: The node is doing initial slot creation or an initial dump and load".
But i can't tell you why this nodes are in this state.
Regards, Andreas
Did-you chec
Thanks, I removed the other nodes from bdr.bdr_nodes table, deleted all the
bdr_connections and pg_replication_identifier entries, dropped the
pg_replication_slots restarted the instance and then trying the ALTER statement
resulted in:
ERROR: No peer nodes or peer node count unknown, cannot ac
Yes, bdr_connections had the same number of rows:
deliver=# select * from bdr.bdr_connections;
conn_sysid | conn_timeline | conn_dboid | conn_origin_sysid |
conn_origin_timeline | conn_origin_dboid | conn_is_unidirectional |
I am trying to repair a broken bdr cluster setup and so far everything I tried
failed. Under the original node that ran bdr.bdr_group_create I am getting the
following error:
2015-12-04 19:34:29.063 UTC,,,22991,,5661eac4.59cf,1,,2015-12-04 19:34:28
UTC,3/0,0,ERROR,55000,"previous init failed, m
Thanks David,
This helped me to understand the WAL importance.
Finally, we decided to use "stream" option to copy the WAL file during the
backup as mentioned in the help.
Enabled this options in postgres.conf
wal_level = hot_standby
max_wal_senders = 2
Though I get the information, which are
16 matches
Mail list logo
