Is there something in the PostgreSQL source tree
that I should change, for example hacking in:
src/backend/utils/mb/conversion_procs
Thanks alot,
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Hello Karsten,
On Tues., Feb 08, 2011, Karsten Hilbert wrote:
>On 8 February 2011 10:39, Michael wrote:
>> I'm trying to view text data stored by OpenSIPS 1.6.4 (the latest)
>> as BLOB
>
>I take it you mean BYTEA.
>
That's probably correct, yes.
>> and P
Hello Thom,
I sent this accidentally to you directly, here's a copy for the
list as well.
On Tues., Feb 08, 2011, Thom Brown wrote:
>On 8 February 2011 10:39, Michael wrote:
>> opensips=> select * from sip_trace;
>> id | time_stamp | callid | traced_user | msg | method |
Hello Thom,
On Tues., Feb 08, 2011, Thom Brown wrote:
>On 8 February 2011 12:45, Michael wrote:
>> On Tues., Feb 08, 2011, Thom Brown wrote:
>>>On 8 February 2011 10:39, Michael wrote:
>>>> opensips=> select * from sip_trace;
>>>> id | tim
Hello Karsten,
On Tues., Feb 08, 2011, Karsten Hilbert wrote:
>On Tue, Feb 08, 2011 at 02:19:49PM +0100, Michael wrote:
>>>> The arrow in the last line indicates that 'convert_from' is not
>>>> correctly parsed.
>>>>
>>>My understanding w
Hello Thom,
On Tues., Feb 08, 2011, Thom Brown wrote:
>On 8 February 2011 13:43, Thom Brown wrote:
>> On 8 February 2011 13:19, Michael wrote:
>>> On Tues., Feb 08, 2011, Thom Brown wrote:
>>>>On 8 February 2011 12:45, Michael wrote:
>>>>> On Tues
Hello Thom,
On Tues., Feb 08, 2011, Thom Brown wrote:
>On 8 February 2011 13:43, Thom Brown wrote:
>> On 8 February 2011 13:19, Michael wrote:
>>> On Tues., Feb 08, 2011, Thom Brown wrote:
>>>>On 8 February 2011 12:45, Michael wrote:
>>>>> On Tues
Hello Thom,
On Tues., Feb 08, 2011, Thom Brown wrote:
>On 8 February 2011 14:30, Michael wrote:
>> On Tues., Feb 08, 2011, Thom Brown wrote:
>>>On 8 February 2011 13:43, Thom Brown wrote:
>>>> On 8 February 2011 13:19, Michael wrote:
>>>>> On Tues
On Tues., Feb 08, 2011, Thom Brown wrote:
>On 8 February 2011 19:28, Andreas Kretschmer wrote:
>> Thom Brown wrote:
>>> On 8 February 2011 18:45, Andreas Kretschmer
>>> wrote:
>>>> Michael wrote:
>>>>> I'm trying to view text d
pping new
> drivers with our applications.
>
> GPL is a poison pill when it comes to groups like us that are trying
> to develop standards (and shared code bases) that can be used by both
> opensource and corporate types alike.
>
> So keep up the good wo
I am trying to move a postgresql database from one
server to another. The original server is 7.1.3, and
the new one is 7.3.4.
I went on the old and used the command:
pg_dumpall > dump
On the new:
psql -e < dump
I get this for multiple functions. (Error follows
surrounded by *'s)
CREATE FUN
Whats the minimum hardware anyone has installed Postgresql on ?
Someone is thowing out some old pc's and thought I might make use of
one.
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://www.postgresql.org/search.mpl
Guy Fraser wrote:
>
> Hi
>
> I would appreciate it if the MySQL zealots with troglodytical
> mentalities would confine themselves to there own mailing list.
>
I've yet to see any MYsql zealots on this list.
> The odd comparison is OK but the flame wars are a waste of storage.
>
> MySQL and Po
http://www.zend.com/zend/art/databases.php
Needless to say Postgresql comes out looking pretty good. Good to have
links like this to show the advantages of Postgresql when I'm trying to
convert others to using it.
---(end of broadcast)---
TIP 2: yo
Hi all
I have just isolated a big problem in one of my applications and it turns out
to be a memory leak in postgresql on a VERY basic piece of functionality
It just caused a backend to grow to 133 MB in 4 hours running, which is
obviously not good
Simple piece of C code to demonstrate this:
Hi
I am about to upgrade a server that is about to be running a large and busy
postgresql database
currently it has
128 MB 100 MHz SDRAM
AMD K6-2/300 CPU
10 GB 7200RPM 9.0ms IBM IDE HDD
It will, over the next few months, as money becomes available, be upgraded to:
256 MB 100 MHz SDRAM
Dual At
me other number in "serial" in the main
table to no avail. What is the magic to get this to work. There
appears to be no documentation anywhere on the necessary SQL commands
to cycle the generator. I've tried the method used for Oracle SQL but
that does not work. I'm a bit o
ommands
> > to cycle the generator. I've tried the method used for Oracle SQL but
> > that does not work. I'm a bit of a newbie at this.
> >
> > Michael
> > [EMAIL PROTECTED]
>
> You cant insert into a serial as far as I know.
>
> The serial
and accessible through psql. The script looks like this:
View Database Records
item vendorname quantity
My PostgreSQL was installed to require user authorization, so I've tried
modifying the pg_connect line in the tutorial script like so:
$conn = pg_Connect("dbname=grocery user=mstrait p
One of my sons was hired by Google last year after spending the past
several years working on various open-source projects, it took 2 days of
back-and-forth with Google's legal department before he was satisfied with
the restrictions in their offer.
--
Mike Nolan
On Wed, Mar 11, 2015 at 4:46 PM, J
g is the header that is present in one of the Unicode files.
I am no lawyer, but FWIW I have never heard of any legal folks I know
complain about this license being incompatible with PostgreSQL
license.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make
, so you are missing 4 years worth of
bug fixes, the latest minor version of the 9.0.X release being 9.0.19.
Note as well that 9.0 will be EOL at the end of the year, hence you
could do even better: an upgrade to a newer major version.
Regards,
--
Michael
--
Sent via pgsql-general mailing list (p
postgresql.conf is a perfect method to corrupt
your data, you should really not set it to off.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
ISTS
in 9.4 and 9.3:
http://www.postgresql.org/docs/9.3/static/sql-createtableas.html
http://www.postgresql.org/docs/9.4/static/sql-createtableas.html
But it does in 9.5 and onwards:
http://www.postgresql.org/docs/devel/static/sql-createtableas.html
Regards,
--
Michael
--
Sent via pgsql-gener
ts new
value taken into account.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
>
The user whose password has visibly been lost is not the database user
postgres, but the OS user postgres. If you have root on this server access,
simply enforce the password to a new value.
--
Michael
pgsql-novice I guess...
JSON is a data type:
http://www.postgresql.org/docs/devel/static/datatype-json.html
So what you need to do is at least to create a table with a column having
as data type JSON, and then insert data into it:
=# CREATE TABLE json_tab (data json);
CREATE TABLE
=# INSERT INTO json_tab VALUES ('{"key":"value","key2":"value2"}');
INSERT 0 1
=# select * from json_tab ;
data
-
{"key":"value","key2":"value2"}
(1 row)
--
Michael
On Mon, Mar 30, 2015 at 7:11 PM, Michael Paquier
wrote:
>
>
>
> On Mon, Mar 30, 2015 at 6:54 PM, Kavi wrote:
>
>>
>> I sample data as below-
>>
>>
>> {
>> "glossary": {
>> "title":
s needed to add
in the index entries for the tuples that have been inserted into the table
during the build phase.
--
Michael
a1. Still, I would just
suggest getting the raw source code from git from one of those two
places:
http://git.postgresql.org/gitweb/?p=postgresql.git;a=summary
https://github.com/postgres/postgres
You are sure it will be there on branch master.
--
Michael
--
Sent via pgsql-general mailing li
/ms681385%28v=vs.85%29.aspx
So first check your file system, and be sure that you have a backup around.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
o perhaps-stupid things. As that's a btree right split,
perhaps you could recover your data by ignoring this index...
> Unfortunately, I only have a backup on February. Is there a way I can recover
> it without losing the recent data?
What is lost is lost. A good backup strateg
to query table for different customer together.
I wonder which I should use, different shema or different database to store
data?
I 'd like to know the advantage and disadvantage for using schema or database.
Thanks
michael
--
Sent via pgsql-general mailing list (pgsql-ge
Thanks for your suggestion.
I'd like to use schema as you suggest.
yours, michael
On Mon, 13 Apr 2015 11:20:59 +0900
Ian Barwick wrote:
> On 13/04/15 11:08, Michael Cheung wrote:
> > hi, all;
> >
> > I am new here. And I need some suggestion.
> >
> >
Thanks for your additional comment.
It is more clear, I'd better to using schema more than using database.
yours, michael
On Sun, 12 Apr 2015 19:24:30 -0700
John R Pierce wrote:
> On 4/12/2015 7:20 PM, Ian Barwick wrote:
> > If as you say access to the database is via a sing
creating all my databases or initialize PGSQL?
You can enforce the collate used in an ORDER BY clause:
SELECT a, b, c FROM tbl WHERE ... ORDER BY a COLLATE "C";
http://www.postgresql.org/docs/devel/static/sql-expressions.html#SQL-SYNTAX-COLLATE-EXPRS
Regards,
--
Michael
--
Sent via pgsq
from 2013?
Sorry, it seems I missed this email. Yes, the code should be
thread-aware, at least I don't know of any problems with it. It appears
to me that the docs haven't been updated by the patch that made ecpg
work with threads back in the day.
Michael
--
Michael Meskes
Michael at Fam-Me
e to 9.1.15. You are missing 3
years worth of many bug fixes, some of them being critical.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Hello,
I recently installed a PostgreSQL server to this spec:
server v9.3.6
EnterpriseDB mongo_fdw vREL-4_0_0
libbson v1.1.5
mongo C driver v1.1.5
and Mongo is at 2.7.1. Mapping fields in Mongo documents, including _id,
has been successful, with the exception of nested fields. Assuming my Mongo
On Mon, May 18, 2015 at 7:04 PM, Sachin Srivastava
wrote:
> Hi Michael,
>
> So, as per your suggestion I'll update my database from 9.1.2 to 9.1.15.
>
> Kindly confirm, which year this 9.1.2 was released and when 9.1.15 was
> released.
>
>
> And easily I can upg
http://www.postgresql.org/docs/devel/static/xfunc.html
Perhaps you are looking for something in C, now it would be less
complex to do it for example with pl/pgsql or another language, and
call it from a C client with a correct set of arguments satisfying
your needs.
--
Michael
--
Sent via pgs
The documentation for pg_dump says that dump files are created in a
consistent state.
Is that true across multiple tables in the same pg_dump command?
(Obviously it would not be true if I dumped tables using separate pg_dump
commands. But if I put the database into a backup state using
'pg_start_
On Wed, May 20, 2015 at 12:40 PM, David G. Johnston <
david.g.johns...@gmail.com> wrote:
> Yes. The entire dump is performed within a single transaction.
>
> On Wed, May 20, 2015 at 9:24 AM, Michael Nolan wrote:
>
>> The documentation for pg_dump says that dum
the new value to it the existing field, jsonb has as property
to enforce key uniqueness, and uses the last value scanned for a given
key.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Sat, May 30, 2015 at 9:10 PM, Andreas Kretschmer
wrote:
> Michael Paquier wrote:
>
>>
>> Append the new value to it the existing field, jsonb has as property
>> to enforce key uniqueness, and uses the last value scanned for a given
>> key.
>
> can you sh
y matched ? Like for the above example, I
> see only 2 matched found.
You could use "?" to do the check for each individual key, and then
count how many matched...
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Fri, Jun 5, 2015 at 12:23 PM, Casey Deccio wrote:
> I have a database in which one table references the primary key of
> another. The type of the primary key was initially int, but I changed it
> to bigint. However, I forgot to update the type of a column that
> references it. So, I've init
subsequent versions of Postgres?
Are there any plans to make a built-in datatype, like ,
o, or the various Geometric Types (eg, )?
Michael Shapiro
Senior Systems Engineer
National Center for Supercomputing Applications (NCSA)
University of Illinois, Urbana-Champaign (UIUC)
Hi Melvin,
Thanks for this response. It still leave my question unanswered. I should
rephrase it -- will become a native datatype in Postgres (as
opposed to remaining an extension). Are there any plans to make a
native datatype?
Michael
On Fri, Jun 12, 2015 at 7:58 AM, Melvin Davidson
wrote
sumption that
replication lag measured in terms of timestamp is a good thing while
it should be estimated in terms of byte difference by comparing WAL
positions between the master and its standbys?
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
differs for 1 megabyte.
> ps: sorry for my English
>
>
> On 06/15/2015 02:57 AM, Michael Paquier wrote:
>>
>> Isn't your mistake the fact that you rely on the assumption that
>> replication lag measured in terms of timestamp is a good thing while
>>
they work as expected. Giving a try with worker_spi on
9.4, I see no problems as well:
$ ps ux | grep bgworker
michael 3906 0.0 0.1 2594780 7456 ?? Ss8:21AM 0:00.02
postgres: bgworker: worker 1
michael 3905 0.0 0.1 2594780 6996 ?? Ss8:21AM 0:00.02
case char_1.out seems to match.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Fri, Jun 19, 2015 at 8:29 AM, 夏高 wrote:
> Thanks Michael! Could you tell me which option determines what expected
> output is used?
Have a look at results_differ() in pg_regress.c ;) The file selected
as expected output is the one with less lines of diffs.
--
Michael
--
Sent via
refer to conserve this bandwidth and write the files to a
> local archive on any active standby.
>
Both methods you mentioned are the way to go for now I am afraid, or you
wait for 9.5.
Regards,
--
Michael
On Tue, Jun 23, 2015 at 8:18 PM, Leif Gunnar Erlandsen
wrote:
> Is it possible to use a replication_slot for a downstream-server when
> setting up cascading replication on 9.4
Yes. Just be careful that replication slot data is not included in a
base backup.
--
Michael
--
Sent via
standby then you will need to take a
new fresh base backup knowing that you are using 9.2.
Regards,
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
reat.
>
How to promote a node: pg_ctl promote or use a trigger_file:
http://www.postgresql.org/docs/devel/static/warm-standby.html#STANDBY-SERVER-OPERATION
Turning temporarily off replication has little meaning if you intend to
bring back a new standby afterwards.
My 2c.
--
Michael
as well as the PostgreSQL wiki have all the
documentation to help you achieve those steps.
Regards,
--
Michael
other recommend the same,
simply let the existing standby alone and create a new instance by taking a
new base backup from either the master or the standby and use it for your
tests. Then eliminate the node you created. In short: avoid doing stupid
things...
--
Michael
from the ctid?
Isn't it something that pageinspect can do directly for you? It has
been extended for brin indexes.
http://www.postgresql.org/docs/devel/static/pageinspect.html
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make chan
On 7/6/15, Robert DiFalco wrote:
> I'm not sure how to create a result where I get the average number of new
> users per day of the week. My issues are that days that did not have any
> new users will not be factored into the average, giving an overinflated
> result.
>
> This is what I started wit
On Mon, Jul 6, 2015 at 5:50 PM, David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Mon, Jul 6, 2015 at 6:16 PM, Michael Nolan wrote:
>
>> > But you can see it wont give correct results since (for example)
>> Monday's
>> > with no new user
Here's a minor refinement that doesn't require knowing the range of dates
in the users table:
(select created, created as created2, count(*) as total from users
group by 1, 2
union
(select generate_series(
(select min(created)::timestamp from users),
(select max(created)::timestamp from users),
'1
On Sat, Jul 11, 2015 at 4:53 PM, Vincent Veyron wrote:
> On Sat, 11 Jul 2015 16:55:44 -0400
> Dane Foster wrote:
> . After a while, you'll find your way around the documentation.
>
> I've been doing it almost every day for years, still learning every time.
>
I highly recommend reading the d
no option regarding that, and ALTER TABLE ADD
CONSTRAINT prevents its creation.
--
Michael
stions, still most of the people picking up patches from -docs also
usually have a look here.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
wer to both questions is in the error message:
upgrade your system to a newer kernel or migrate to a newer server.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
indly suggest why this
> problem is coming.
You are trying to connect to a system that is performing a crash
recovery, meaning that it crashed, and you cannot connect to it, or
this is a standby node that is not set up as a read-only hot standby.
--
Michael
--
Sent via pgsql-general ma
s of no
> help.
Visibly your data is already lost in alpha_45... Hence if you can
recover this database from an older backup you had better do it. Now
perhaps other folks here have other recommendations and strategies
though :)
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@p
On Mon, Jul 20, 2015 at 7:00 PM, Ramesh T wrote:
> Hi All,
> What i need to know for postgres recovery..?let me know in detail.
Documentation is always a good start:
http://www.postgresql.org/docs/devel/static/backup.html
--
Michael
--
Sent via pgsql-general mailing list
ruser. You can define user with such rights
with CREATE ROLE with the keyword REPLICATION:
http://www.postgresql.org/docs/devel/static/sql-createrole.html
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
to/openssl)
You could use CFLAGS and LDFLAGS for this purpose:
./configure CFLAGS="-I/usr/openssl-0.9.8zg/include" \
LDFLAGS="-L/usr/openssl-0.9.8zg/lib" \
--with-openssl
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
ed and then check your distribution
packages or the toolchain you are trying to build the code on.
> A bug?
I don't think so.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
st transaction ID that a given backend is currently seeing.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
ay to restore a backup depends on the format a dump has been taken:
http://www.postgresql.org/docs/devel/static/app-pgdump.html
Except the plain format that need psql, all the others (custom,
directory and tar) need pg_restore.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@pos
I'm pushing to get this box into
production later this week!
Thank you in advance,
Michael
-
I just sent this message to psql-admin and realised this may be the more
appropriate location to ask.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
current shell.
Thanks for your time,
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
location to update system services stack depth?
#This file sets the resource limits for the users logged in via PAM.
postgres will not be 'logged in' via PAM.
#It does not affect resource limits of the system services.
well what does!??
Thanks
Michael
Bye,
Chris.
--
Sent v
a little update,
I've tried the instructions at this URL:
https://ma.ttias.be/increase-open-files-limit-in-mariadb-on-centos-7-with-systemd/
I either get the same errors appear when I run systemctl daemon-reload;
systemctl restart postgresql-9.4
Aug 17 09:08:49 db1 pg_ctl[3343]: < 2015-08-17
s and just report that number back?
attempting to adjust systemd LimitSTACK parameter for the service is
proving more difficult than anticipated.
thanks
Michael
On 17/08/15 09:16, Michael H wrote:
a little update,
I've tried the instructions at this URL:
https://ma.ttias.be/increase-o
Hi Tom,
I've ran systemctl damon-reload; systemctl restart postgresql-9.4 and
also tried rebooting. none of these options are working.
Michael
On 17/08/15 14:47, Tom Lane wrote:
Michael H writes:
I've tried the instructions at this URL:
https://ma.ttias.be/increase-open-file
8/15 19:07, Gordon Messmer wrote:
On 08/17/2015 03:34 AM, Michael H wrote:
the [Service] section -
[Service]
LimitSTACK=12288
...
By the errors I will assume that it should be in the [Service] section.
I couldn't find confirmation of this online...
Yes, it belongs in the [Service] section.
$ m
d now I'm cursing it!
any info would be appreciated,
thanks
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
wal_buffers=64MB
shared_buffers=60GB
work_mem64MB
Other settings were changed and reverted again due to performance decreases.
I also dropped shared_buffers down to 32GB, TPS dropped further.
On 18/08/15 16:12, Joshua D. Drake wrote:
On 08/18/2015 08:01 AM, Michael H wrote:
Hi
I have tested all different shared_buffers settings across both
versions, from 8GB - 60GB. 8-32GB were optimal. in reality the
difference from 8 - 32 was minimal.
On Tue, Aug 18, 2015 at 11:49 AM, Jeff Janes mailto:jeff.ja...@gmail.com>> wrote:
On Tue, Aug 18, 2015 at 8:01 AM, Michael H
made two configuration changes (shared_buffers and work_mem)
and the stats were smashing 9.1.
I think I just expected the same kind of performance increase (or
atleast the same performance) when I went to 9.4.
I'm not expecting a 20% increase against 9.2.13, but I do expect to see
the same increase ag
ing 9.2.13 (provided from CentOS base) with the intention of
staying with that version.
Then I wanted to see better TPS on high client numbers and moved to 9.4,
even this took a little persuasion with my colleague... 9.5 is
definitely a no.
Thanks
Michael
--
Sent via pgsql-general ma
Hi Joshua,
On 18/08/15 16:12, Joshua D. Drake wrote:
On 08/18/2015 08:01 AM, Michael H wrote:
Hi,
I've been tuning our new database server, here's some info...
CentOS Linux release 7.1.1503 (Core)
3.10.0-229.11.1.el7.x86_64
8 x 16GB 1600MHz PC3-12800 DDR3- 128GB tot
a bad kernel for postgresql-9.4???
Michael
On 19/08/15 10:00, Michael H wrote:
CentOS Linux release 7.1.1503 (Core)
3.10.0-229.11.1.el7.x86_64
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
n the primary
> and standby".
>
This means that you are trying to use a standby that has been set up using
the base backup from the node of another cluster (be it either standby or
master node), different than the node you are trying to connect to. This
error just reports the incompatibility.
--
Michael
versions you are going to need some manual
operations before being able to run the standby and the master on the
same server.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
the master.
That's not a bug, just an operation mistake.
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
anges at the end of the
> file
> in one place for easy maintenance.
The last value read for a parameter is the effective one. This counts
as well for included configuration files. The configuration file
managed by ALTER SYSTEM has the priority over the rest.
--
Michael
--
Sent via pgsql
On Wed, Sep 9, 2015 at 11:24 PM, Igor Neyman wrote:
> Could you please provide reference to pg_audit?
Should be here:
http://pgaudit.org/
https://github.com/pgaudit/pgaudit
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscript
Hi,
In Production, I have a DB2 which is replicated partially using Londiste
from DB1. I make file-system backups nightly on both DBs.
Last Monday, when I restored the backup made from DB2 to a test server,
Postgres(9.3.5) started up fine. But, I found out that the primary key of
one of the table
DB1
and DB2 that morning. But, I don't think that it harms anything.
Thanks
On Thu, Sep 17, 2015 at 4:53 PM, Adrian Klaver
wrote:
> On 09/17/2015 04:31 PM, Michael Chau wrote:
>
>> Hi,
>>
>> In Production, I have a DB2 which is replicated partially using Londiste
&
e:
>>
>>> Le 18 sept. 2015 5:23 AM, "Adrian Klaver" >> <mailto:adrian.kla...@aklaver.com>> a écrit :
>>> >
>>> > On 09/17/2015 05:37 PM, Michael Chau wrote:
>>> >>
>>> >> To restore on test
tgreSQL. I think that I will pursue this.
Thanks again.
On Fri, Sep 18, 2015 at 2:40 PM, David Steele wrote:
> On 9/18/15 3:44 PM, Michael Chau wrote:
>
>> Hi Jeff,
>>
>> Only if you are very lucky. If your tar command tars up the pg_xlog
>>> directory as the last
like
2015-09-22 12:02:59.836 +0200.
How can I setup Postgres to log with a numerical offset in the CSV
logs and not with the name of the time zone?
Any hints and links to the corresponding documentation would be appreciated.
Regards,
Michael
--
Sent via pgsql-general mailing list
1 - 100 of 3411 matches
Mail list logo
