Groskreutz: Please kindly.


Routhier: DrJ: don’t do this

Ferrato: That’s what I’m doing.

Karwowski: DrJ: is an easy way to share your schema, your data, and the queries you’re testing. It saves us time and makes it more likely that you’ll get an answer! Make sure you set it to use MySQL.

Rarang: How can I do SELECT field as FUNCTION

Labore: Where the name will becomes the result of function

Helmsing: DrJ: can you rephrase that?

Naslund: No, you can’t do that

Helmsing: Naslund: I commend you for understanding what he said.

Kilker: Oh come on, what I said is as clear as day :

Kanno: Set the value of a variable as the function result, use it as an alias

Fasula: Exactly, but I said it better

Kanno: If by better you mean incoherent, yes

Gorrindo: Is there a solution for this — 150923 23:53:31 ERROR innobase_buffer_pool_size can’t be over 4GB on 32-bit systems

Nardone: Please, how can i specify with group by id_user to picku up in select newer record which is specified in column created?

Buchta: Innodb returns error when its buffer pool is set below 4G. but can’t have 4G on x86 system

Bidgood: Tomatto:

Warley: Haris: you get that error with a buffer pool smaller than 4G?

Routhier: Haris: are you on windows?

Warley: Haris: what value are you trying to use?

Warley: Why on earth are you using a 32-bit linux kernel in 2015.

Helmsing: Use a cloud box, and upgrade your box in the meantime!

Warley: Haris: can you show the whole error log?

Routhier: Why were you using 32 bit in 2011?

Helmsing: You can rent those things, you know.

Lynema: Routhier: THAT . was not me

Routhier: I dont think it works above ~1.4G iirc

Warley: Haris: you obviously aren’t using innodb_buffer_pool_size=3072. maybe you’re using 3072M? at any rate, you’re not providing a very clear or comprehensive picture of what is going on.

Routhier: Never tested multiple buffer pools on 32bit, which version of mysql?

Warley: Haris: can you show the whole error log?

Antos: On 32bit systems the whole mysql server process can’t get hold of more than 4GB memory best case. with other address space being needed, typically at ~3GB you read the end of the line. also depending on glibc its possible that a single chunk of allocation can’t be largen than 2GB ie your innodb buffer pool

Quintania: Haris: you could try to use 4 innodb buffer pool instances, each 768M large.

Kopatz: Haris:

Bettini: Haris: available since 5.5.4

Iuliano: Haris: but, honestly – upgrade to 64 bit :

Wardall: Helmsing: i am not sure if it is what i want, ‘id_user’ and ‘created’ columns i want to pick up in group by id_user a record which has newer created date by that grouped user

Warley: Haris: use a smaller buffer pool.

Dedrick: Is there a way without subquery?

Hyndman: Isn’t mysql built for el6 compiled with pae support ?

Routhier: Haris: that lets the kernel address more ram, not a single allocation however

Zhuang: Haris: pae support means: the whole system kernel can cope with more than 4GB of RAM.

Portis: Yep. this is not a kernel issue centos guys tell me

Routhier: Groskreutz: thanks for confirming that instances should solve the problem

Bottrell: Groskreutz: Please kindly provide me a config example