On Fri, Feb 10, 2017 at 7:15 PM, Jehan-Guillaume de Rorthais
wrote:
> On Thu, 9 Feb 2017 18:27:30 +
> Rakesh Kumar wrote:
>
>> >Sure, but when you are doing a switchover, the standby is supposed to be
>> >connected to the master when you shutdown the master. So based on the doc,
>> >the stand
>> Kill ? You mean "pg_ctl stop -m fast" right ?
Yes.
>Use timeline to resync ? Timeline is an internal mechanism in PostgreSQL, not
>a tool, so I don't get this step...You mean using pg_rewind ?
pg_rewind which uses timeline.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql
On Thu, 9 Feb 2017 18:27:30 +
Rakesh Kumar wrote:
> >Sure, but when you are doing a switchover, the standby is supposed to be
> >connected to the master when you shutdown the master. So based on the doc,
> >the standby should receive **everything** from the master before the master
> >actuall
On Fri, Feb 10, 2017 at 2:42 AM, Jehan-Guillaume de Rorthais wrote:
> On Thu, 9 Feb 2017 10:41:15 +1100
> Venkata B Nagothi wrote:
>
> > On Thu, Feb 9, 2017 at 4:53 AM, Benoit Lobréau >
> > wrote:
> >
> > > Hi,
> > >
> > >
> > > I would like to clarify something about standby promotion. From th
>Sure, but when you are doing a switchover, the standby is supposed to be
>connected to the master when you shutdown the master. So based on the doc,
>the standby should receive **everything** from the master before the master
>actually shutdown.
We use 9.5 and even in that version there is no han
On Thu, 9 Feb 2017 10:41:15 +1100
Venkata B Nagothi wrote:
> On Thu, Feb 9, 2017 at 4:53 AM, Benoit Lobréau
> wrote:
>
> > Hi,
> >
> >
> > I would like to clarify something about standby promotion. From the
> > sentence below. I understand that, during the promotion process, postgres
> > will r
hi,
Tank you for the confirmation !
For the second part, I understand your explanation but I fail to see how
checking what we have replayed against what we have received will confirm
we have received everything (unless we are in sync replication).
Have a good day !
Benoit.
On Thu, Feb 9, 2017 at 4:53 AM, Benoit Lobréau
wrote:
> Hi,
>
>
> I would like to clarify something about standby promotion. From the
> sentence below. I understand that, during the promotion process, postgres
> will replay all the available wals (from the archive or pg_xlog).
>
Yes, that is cor
What were the ramifications of the bug? I don't see any details in the
release notes. It is not really an option to upgrade before the move.
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Clarification-on-CONTEXT-xlog-redo-xid-assignment-tp5059725p5060301.html
Sent
On Thu, Dec 8, 2011 at 6:37 PM, kc5 wrote:
> Dec 7 12:40:55 postgres[28199]: [ID 748848 local2.info] [5-1] LOG: file
> "pg_subtrans/8732" doesn't exist, reading as zeroes
> Dec 7 12:40:55 postgres[28199]: [ID 748848 local2.info] [5-2] CONTEXT:
> xlog redo xid assignment xtop 2268215780: subx
By default it has no Init options, so it doesn't check for stopwords.
In the first place, this functionality is a rip-snorting home run on
Postgres. I congratulate Oleg who I believe is one of the authors.
In the second, I too had not read (carefully) the documentation and am
very happy
Andreas,
I'd create myself copy of dictionary to be independent on system changes.
Oleg
On Thu, 22 Jul 2010, Andreas Joseph Krogh wrote:
On 07/22/2010 07:44 PM, Oleg Bartunov wrote:
Don't guess, but read docs
http://www.postgresql.org/docs/8.4/interactive/textsearch-dictionaries.html#TEXTSEAR
On 07/22/2010 07:44 PM, Oleg Bartunov wrote:
Don't guess, but read docs
http://www.postgresql.org/docs/8.4/interactive/textsearch-dictionaries.html#TEXTSEARCH-SIMPLE-DICTIONARY
12.6.2. Simple Dictionary
The simple dictionary template operates by converting the input token
to lower case and
Don't guess, but read docs
http://www.postgresql.org/docs/8.4/interactive/textsearch-dictionaries.html#TEXTSEARCH-SIMPLE-DICTIONARY
12.6.2. Simple Dictionary
The simple dictionary template operates by converting the input token to lower
case and checking it against a file of stop words. If it i
On 07/22/2010 06:27 PM, John Gage wrote:
The easiest way to look at this is to give the simple dictionary a
document with to_tsvector() and see if stopwords pop out.
In my experience they do. In my experience, the simple dictionary
just breaks the document down into the space etc. separated w
The easiest way to look at this is to give the simple dictionary a
document with to_tsvector() and see if stopwords pop out.
In my experience they do. In my experience, the simple dictionary
just breaks the document down into the space etc. separated words in
the document. It doesn't anal
Hello
2009/12/25 m. hvostinski :
> Hi,
>
> I would appreciate if someone could clarify the aspects of using array
> columns.
>
a) don't use array column as storage for list of foreign keys. It is
one basic and significant rule. Planner and optimizer cannot work well
with keys stored in arrays. So
> "m" == m hvostinski writes:
m> I would appreciate if someone could clarify the aspects of using array
m> columns.
In general, bad idea.
m> We need to store up to ten related integer values per row and currently it
m> is implemented as a varchar column that holds a string that is concatena
>So in practice, should one vacuum template1 when
> vacuuming other database (Assuming one doesn't use vaccumdb
> script when vacuuming database)?
In practice, it shouldn't be a big deal to vacuum template1 once in a
while, because, since it shouldn't have much data other than
pg_catalog ta
>
> Yes: the wraparound limit is for transactions
> cluster-wide, not per
> database. If you make 1 change in template1 and then 2
> billion
> changes in some other databases, template1 is broken
> unless it's
> been vacuumed meanwhile.
>
> regards, tom lane
>
So in pr
Ludwig Isaac Lim <[EMAIL PROTECTED]> writes:
> Under normal circumstances, there's no need to vacuum
> template1 right?
Only if it hasn't been modified.
> Its quite difficult to imagine XID
> wraparound problems occuring in template1. I can't think
> how can 4 billion transactions occur in temp
ElayaRaja S <[EMAIL PROTECTED]> writes:
> bash-2.05b$ pg_ctl stop
> /usr/local/pgsql/bin/pg_ctl: line 274: kill: (19859) - No such process
> waiting for postmaster to shut
> down
> failed
> pg_ctl: postmaster does not shut down
Is the
ashley <[EMAIL PROTECTED]> writes:
> I wish to run postgresql on a Linux (Slackware) server over a LAN.
> The client must reside on Apple MacIntosh (12 of them)
What are you planning to write the client in?
If you haven't decided yet, one possibility is Tcl. It runs fine on
Macs. I'm not sure
]
Subject: Re: [GENERAL] Clarification
> > that too is an option but it would hurt me to have to insert 20K
record
> > or
> > something like that with a web browser.
>
> H How ODBC driver is supposed to help with that? Upload a CSV
or
> FF file and run bulk i
> > that too is an option but it would hurt me to have to insert 20K record
> > or
> > something like that with a web browser.
>
> H How ODBC driver is supposed to help with that? Upload a CSV or
> FF file and run bulk insert with COPY.
with ODBC:
user load the database client app (
> that too is an option but it would hurt me to have to insert 20K record
> or
> something like that with a web browser.
H How ODBC driver is supposed to help with that? Upload a CSV or
FF file and run bulk insert with COPY.
> maybe because it is/was a deal between Apple and HK to b
> Not actually necessary. After all, make client part do what it's supposed
> to- get user input and display server responses. Browser on Macs and
> HTTP/CGI + PGSQL on the server will do in most cases.
that too is an option but it would hurt me to have to insert 20K record or
something
> the only thing remaining to know is if
> there's PostgreSQL ODBC-like drivers for MacOS and/or applications able
> to
> work with PostgreSQL.
Not actually necessary. After all, make client part do what it's supposed
to- get user input and display server responses. Browser on Macs and
> As I've recieved some "interesting" emails to clarify:
>
> I wish to run postgresql on a Linux (Slackware) server over a LAN.
>
> The client must reside on Apple MacIntosh (12 of them)
>
> I am not familair with any client that will allow this. I have no
> problem with Linux or mac, I have very
29 matches
Mail list logo
