Dear Jaime,
Is there commercial solution that uses the same concept of wal streaming and
allows the Creation of temp tables on slave
I really appreciate your help
Thanks and Regards,
Sally Nayer
IT Systems Senior Engineer
TE Data
TE Data, Building A11- B90, Smart Village
Cairo- Alex Dese
The following bug has been logged online:
Bug reference: 6267
Logged by: Maksym Boguk
Email address: maxim.bo...@gmail.com
PostgreSQL version: 9.0.4
Operating system: Linux 2.6.32-5
Description:Wrong results in pg_database_size
Details:
Somehow pg_database_size prod
The following bug has been logged online:
Bug reference: 6268
Logged by: Roman Lytovchenko
Email address: roman.lytovche...@gmail.com
PostgreSQL version: 9.1.1
Operating system: Mac OS X 10.6.8
Description:multiple update with on cascade
Details:
create table t2 (
On 10/25/11 12:11 AM, Sally Nayer wrote:
Is there commercial solution that uses the same concept of wal streaming and
allows the Creation of temp tables on slave
WAL files represent 'delta changes' between the state of the postgres
file system. *anything* that changes database files on the s
On Mon, Oct 24, 2011 at 16:37, Keith Fiske wrote:
> On Sat, Oct 22, 2011 at 11:49 AM, Tom Lane wrote:
>> "Keith Fiske" writes:
>
>>> If you create a user as a NONsuperuser,
>>> then later ALTER them to be one, they will NOT have the replication
>>> permission and cannot be used as a replication
On Tue, Oct 25, 2011 at 1:39 PM, Magnus Hagander wrote:
> On Mon, Oct 24, 2011 at 16:37, Keith Fiske wrote:
>> On Sat, Oct 22, 2011 at 11:49 AM, Tom Lane wrote:
>>> "Keith Fiske" writes:
>>
If you create a user as a NONsuperuser,
then later ALTER them to be one, they will NOT have the
The following bug has been logged online:
Bug reference: 6269
Logged by: Paul Stapersma
Email address: paul.staper...@gmail.com
PostgreSQL version: 8.3.3
Operating system: Mac OS X Version 10.6.8
Description:Anomaly detection
Details:
Dear reader,
For a project at
"Maksym Boguk" writes:
> Somehow pg_database_size producing results which are 2Ñ
more then reality.
I can't reproduce any such problem here. I suspect you overlooked some
tablespaces in your manual "du" commands.
regards, tom lane
--
Sent via pgsql-bugs mailing list (
Well, it is imaginable for there to be some side mechanism to enable use of
temporary tables on a WAL-based replica, after all, we have leapt through
enough hoops to get read transactions working.
That being said...
A) a solution for how to do this has not yet emerged, so it seems not too
likely
> you can't. this isn't a bug but a known limitation and is documented here:
> http://www.postgresql.org/docs/9.1/static/hot-standby.html#HOT-STANDBY-USERS
>
>> Is there any workaround?
>> How could we create temp database and tables on slave?
>>
>
> not with streaming replication
>
> --
> Jaime Ca
Fresh install. With the "One Click Installer" for Windows from
http://www.postgresql.org/download/windows
On Tue, Oct 18, 2011 at 8:48 AM, Craig Ringer wrote:
> On 10/15/2011 11:21 AM, stephen wrote:
>
>>
>> The following bug has been logged online:
>>
>> Bug reference: 6255
>> Logged by:
Tried on both
PostgreSQL 9.0.4 on x86_64-unknown-linux-gnu, compiled by GCC gcc
(GCC) 4.1.2 20080704 (Red Hat 4.1.2-48), 64-bit
and
PostgreSQL 9.0.3 on x86_64-unknown-linux-gnu, compiled by GCC gcc
(GCC) 4.1.2 20080704 (Red Hat 4.1.2-48), 64-bit
shared_preload_libraries = 'pg_stat_statements,auto_
"Paul Stapersma" writes:
> For a project at my University, we compared PostgreSQL with MySQL's InnoDB.
> In this research, we found several cases in which anomalies where detected
> in Isolation levels that guaranteed not to have these anomalies.
> In short summary:
> - we detected non-repeatable
On 25.10.2011 12:51, Paul Stapersma wrote:
PostgreSQL version: 8.3.3
That is a pretty old version. At least you should use the latest version
in the 8.3 series, which is currently 8.3.16. I'm not sure if there's
been any isolation-related bug fixes since 8.3.3, but I don't see any
reason not
On 25.10.2011 18:42, bricklen wrote:
Tried on both
PostgreSQL 9.0.4 on x86_64-unknown-linux-gnu, compiled by GCC gcc
(GCC) 4.1.2 20080704 (Red Hat 4.1.2-48), 64-bit
and
PostgreSQL 9.0.3 on x86_64-unknown-linux-gnu, compiled by GCC gcc
(GCC) 4.1.2 20080704 (Red Hat 4.1.2-48), 64-bit
shared_preloa
I actually figured it out.. forgot to set the encoding type to UNICODE when
I created the db..!
On Mon, Oct 24, 2011 at 11:38 PM, rihad wrote:
> ERROR: unexpected message type 0x58 during COPY from stdin
>>
>
> One possible reason is running out of disk space while making the backup.
> We had t
"Paul Stapersma" wrote:
> PostgreSQL version: 8.3.3
> A full report on our findings can be found here:
> http://dl.dropbox.com/u/19316575/report.pdf
I would like to independently run your tests, but I don't see
anything in the paper to describe the table(s) used or how they were
populated.
The following bug has been logged online:
Bug reference: 6270
Logged by: Evgeniy Galkin
Email address: unik...@gmail.com
PostgreSQL version: 9.0.4
Operating system: GNU/Linux (Ubuntu 10.10)
Description:Invalid string comparison if the string contains '+' or
'-' sign.
"Evgeniy Galkin" writes:
> I'm trying to compare two strings which are starting with '+' and '-' signs.
> And there is some strange behaviour.
This is fairly standard if you're using a non-C locale. Try creating a
fresh database with LC_COLLATE and LC_CTYPE set to 'C'.
r
On Tue, Oct 25, 2011 at 9:22 AM, Heikki Linnakangas
wrote:
> On 25.10.2011 18:42, bricklen wrote:
>>
>> Tried on both
>> PostgreSQL 9.0.4 on x86_64-unknown-linux-gnu, compiled by GCC gcc
>> (GCC) 4.1.2 20080704 (Red Hat 4.1.2-48), 64-bit
>> and
>> PostgreSQL 9.0.3 on x86_64-unknown-linux-gnu, comp
"Roman Lytovchenko" writes:
> Description:multiple update with on cascade
Yeah, this is a bug all right, see my analysis at
http://archives.postgresql.org/pgsql-hackers/2011-10/msg01361.php
As a stopgap workaround, you could manually rename the triggers
generated by the FK constraint so
bricklen writes:
> The steps to reproduce are pretty simple.
> Set the following in the postgresql.conf file:
> shared_preload_libraries = 'pg_stat_statements,auto_explain'
> custom_variable_classes = 'auto_explain'
> auto_explain.log_min_duration = '10s'
> auto_explain.log_analyze = true
> auto
On Tue, Oct 25, 2011 at 2:01 PM, Tom Lane wrote:
> bricklen writes:
>> The steps to reproduce are pretty simple.
>
>> Set the following in the postgresql.conf file:
>
>> shared_preload_libraries = 'pg_stat_statements,auto_explain'
>> custom_variable_classes = 'auto_explain'
>> auto_explain.log_mi
> "Maksym Boguk" writes:
>> Somehow pg_database_size producing results which are 2х more then reality.
>
> I can't reproduce any such problem here. I suspect you overlooked some
> tablespaces in your manual "du" commands.
>
> regards, tom lane
>
No other tablespaces exists
Maxim Boguk writes:
>>> No other tablespaces exists as can be seen in output of:
>>> SELECT oid,spcname,spclocation,pg_size_pretty(pg_tablespace_size(spcname))
>>> from
>>> pg_tablespace;
>>> oid | spcname | spclocation | pg_size_pretty
>>> ---++---+--
25 matches
Mail list logo
